Create wallet
POST {{baseUrl}}/wallets
Creates a new multi-blockchain wallet.
Identifier
The name and primary identifier (wallet
) for the wallet cannot be changed after creation. It must be 1-127 characters long using only the following characters: 0-9, a-z, A-Z, and -. Defaults to a random GUID when omitted.
Security level
Wallets will be managed by Hardware Secure Modules (HSM). Enhance wallet security by defining securityLevel
as level 2
. This will use FIPS 140-2 Level 2 instead of FIPS 140-2 Level 1.
Note that this functionality is not available for sandbox subscriptions.
Additional attributes
You can provide optional custom data as a collection using the additionalAttributes
property. Additional attributes must not exceed a length of 256 and can be updated via the PATCH /wallets/:wallet
operation.
Example
"additionalAttributes": {
"myCustomId": "a87-yP1"
}
Customer ID
The customerId
property refers to the customer ID being used in the Customers API.
Therefore, you will need to create a customer before being able to create a new wallet.
Wallet blockchain address
You can fetch the blockchain address for the created wallet via the corresponding blockchain endpoint (e.g GET /protocols/eth/wallets/:wallet
).
Request Body
{"wallet"=>"my-wallet", "securityLevel"=>1, "additionalAttributes"=>{"description"=>"example user", "epoch"=>"1631096008"}, "customerId"=>"MyCustomerId"}
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. |
| 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 | | |