Recover wallet
POST {{baseUrl}}/wallets/:wallet/recover
Recovers a purged wallet that was previously deleted by DELETE /wallets/{wallet}.
This endpoint can only recover wallets that have been soft-deleted.
HEADERS
| Key | Datatype | Required | Description |
|---|---|---|---|
If-Match | string | (Optional header) Avoid mid-air collisions by matching a resources ETag | |
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. |
| 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. |
| Accept | string | | |