Update wallet
PATCH {{baseUrl}}/wallets/:wallet
Updates an existing wallet without regenerating the cryptographic keys.
Updating the securityLevel parameter or the wallet name is not supported.
Updating the additionalAttributes property will effectively overwrite all previous attributes.
Example: Update all attributes ```http-client PATCH https://api.tangany.com/custody/wallet/my-wallet Content-Type: application/json
{
additionalAttributes
: {
myKey
: some-string
}
}
```
Example: Update the customer ID ```http-client PATCH https://api.tangany.com/custody/wallet/my-wallet Content-Type: application/json
{
customerId
: 78c483d7-5e6d-488b-981c-2ac4bccca2a5
}
```
If the Content-Type header is set to application/json-patch+json, the partial updating ruleset of JSON Patch RFC6902 applies.
This endpoint returns the ETag header that can be used to prevent overwriting unexpected object states of the API resource. Pass the ETag header value to the If-Match header to reject updating if the resource has changed from the observed state.
Example: add 3 new attributes
```http-client
PATCH https://api.tangany.com/custody/wallet/my-wallet
Content-Type: application/json-patch+json
If-Match: 4003db00-0000-0c00-0000-6038dfb20000
[
{op
: add
, path
: /additionalAttributes/kvc
, value
: false
},
{op
: add
, path
: /additionalAttributes/isCustomer
, value
: true
},
{op
: add
, path
: /additionalAttributes/block
, value
: pending KYC
}
]
```
Example: replace the first and remove the third tag ```http-client PATCH https://api.tangany.com/custody/wallet/my-wallet Content-Type: application/json-patch+json
[
{op
: replace
, path
: /additionalAttributes/kyc
, value
: true
}},
{op
: remove
, path
: /additionalAttributes/block
}
]
```
When using Content-Type: application/json the additionalAttributes property from the request's body will otherwise unrecoverably overwrite the attributes of the given wallet resource.
Request Body
{"additionalAttributes"=>{"customId"=>"a2568"}, "customerId"=>"78c483d7-5e6d-488b-981c-2ac4bccca2a5"}
HEADERS
| Key | Datatype | Required | Description |
|---|---|---|---|
tangany-version | number | (Required) Default header that directs the request towards desired Tangany Custody Api version (e.g 2 directs to Tangany Custody APi v2). |
Supports only major versions. |
| If-Match | string | | (Optional header) Avoid mid-air collisions by matching a resources ETag |
| tangany-request-id | string | | (Optional header) A client provided request ID / idempotency key for the asynchronous transaction
When present, the asynchronous transaction will be identified by the provided ID.
The API rejects all but the first request with a given request ID. This way, you can make sure that a given action (e.g. a transaction) will be executed only once.
A client-generated ID can also be used to deterministically recover a missed API response, for example in the event of a gateway timeout or loss of connection.
The API responds with a 409 Conflict status when a given ID has already been used. See GET /requests/:request for more information.
The value must be between 1 and 36 characters and contain only alphanumeric characters or dashes.
Defaults to a randomly generated value when omitted. |
| Content-Type | string | | |
| Accept | string | | |