Create a new deposit destination for an account. A deposit destination is either a cryptocurrency address or a fiat bank account that can be used to receive funds.
For crypto destinations, the address will be generated for the specified network. For fiat destinations, the server provisions a bank account based on the account’s eligibility and returns the account details along with supported payment rails.
A JWT signed using your CDP API Key Secret, encoded in base64. Refer to the Generate Bearer Token section of our Authentication docs for information on how to generate your Bearer Token.
An optional string request header for making requests safely retryable. When included, duplicate requests with the same key will return identical responses. Refer to our Idempotency docs for more information on using idempotency keys.
1 - 128Request to create a new deposit destination. Provide either crypto-specific details (blockchain address) or fiat-specific details (bank account), matching the chosen type.
Until May 15, 2026, crypto destinations may specify the network via either the deprecated root-level network field or crypto.network. After May 15, 2026, the root-level network field will be removed and only crypto.network will be accepted.
The ID of the Account, which is a UUID prefixed by the string account_, that owns the deposit destination.
^account_[a-f0-9\-]{36}$"account_af2937b0-9846-4fe7-bfe9-ccc22d935114"
The type of deposit destination.
crypto "crypto"
DEPRECATED: Use crypto.network instead. This field will be removed after May 15, 2026. The blockchain network for the deposit destination. Either this field or crypto.network must be provided.
base, ethereum, solana, aptos, arbitrum, arbitrum-sepolia, optimism, polygon, world, world-sepolia "base"
The intended target for deposited funds.
{
"accountId": "account_af2937b0-9846-4fe7-bfe9-ccc22d935114",
"asset": "usd"
}Optional metadata as key-value pairs. Use this to store additional structured information on a resource, such as customer IDs, order references, or any application-specific data. Up to 10 key/value pairs may be provided. Keys and values are both strings. Keys must be ≤ 40 characters; values must be ≤ 500 characters.
{
"customer_id": "cust_12345",
"order_reference": "order-67890"
}Crypto-specific details. After May 15, 2026, this will be the only way to specify the network.
{ "network": "base" }Successfully created deposit destination.
A deposit destination for receiving funds to an account. Can be either a cryptocurrency address or fiat bank account instructions.
The ID of the Deposit Destination, which is a UUID prefixed by the string depositDestination_.
^depositDestination_[a-f0-9\-]{36}$"depositDestination_af2937b0-9846-4fe7-bfe9-ccc22d935114"
The ID of the Account, which is a UUID prefixed by the string account_.
^account_[a-f0-9\-]{36}$"account_af2937b0-9846-4fe7-bfe9-ccc22d935114"
The type of deposit destination.
crypto "crypto"
DEPRECATED: Use crypto.address instead. This field will be removed after May 15, 2026.
1 - 128"0x742d35Cc6634C0532925a3b844Bc454e4438f44e"
DEPRECATED: Use crypto.network instead. This field will be removed after May 15, 2026.
base, ethereum, solana, aptos, arbitrum, arbitrum-sepolia, optimism, polygon, world, world-sepolia "base"
Crypto-specific details for this deposit destination. Always populated in responses. Contains the network and address.
{
"network": "base",
"address": "0x742d35Cc6634C0532925a3b844Bc454e4438f44e"
}The status of the deposit destination.
active, inactive, pending "active"
The timestamp when the deposit destination was created.
"2023-10-08T14:30:00Z"
The timestamp when the deposit destination was last updated.
"2023-10-08T14:30:00Z"
The intended target for deposited funds.
{
"accountId": "account_af2937b0-9846-4fe7-bfe9-ccc22d935114",
"asset": "usd"
}Optional metadata as key-value pairs. Use this to store additional structured information on a resource, such as customer IDs, order references, or any application-specific data. Up to 10 key/value pairs may be provided. Keys and values are both strings. Keys must be ≤ 40 characters; values must be ≤ 500 characters.
{
"customer_id": "cust_12345",
"order_reference": "order-67890"
}