Get a specific deposit destination by its ID.
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.
The ID of the deposit address to retrieve.
The ID of the Deposit Destination, which is a UUID prefixed by the string depositDestination_.
"depositDestination_af2937b0-9846-4fe7-bfe9-ccc22d935114"
Successfully retrieved 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_af2937b0-9846-4fe7-bfe9-ccc22d935114"
The ID of the Account, which is a UUID prefixed by the string account_.
"account_af2937b0-9846-4fe7-bfe9-ccc22d935114"
The type of deposit destination.
crypto "crypto"
The cryptocurrency address where funds can be deposited. Format depends on the network (e.g., 0x-prefixed for EVM networks, base58 for Solana).
1 - 128"0x742d35Cc6634C0532925a3b844Bc454e4438f44e"
The blockchain network for the payment. All networks support USDC and USDT.
base, ethereum, solana, aptos, arbitrum, optimism, polygon, sui "base"
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"
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 50 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"
}