Get your deposit address
Issues the deposit address for one asset on one chain, creating the account arrivals are credited to at the same time. The address is static: calling this again for the same asset and chain returns the same address, whatever idempotency key the call carries. A confirmed on-chain transfer to it is credited to that account and announced by a crypto_deposit.credited webhook — see the crypto deposits guide for what happens to anything else that arrives.
Issues the deposit address for one asset on one chain, creating the account arrivals are credited to at the same time. The address is static: calling this again for the same asset and chain returns the same address, whatever idempotency key the call carries. A confirmed on-chain transfer to it is credited to that account and announced by a crypto_deposit.credited webhook — see the crypto deposits guide for what happens to anything else that arrives.
Authorization
bearer In: header
Header Parameters
Your own key for this request, 1-100 characters. Required, here or as the idempotencyKey body field; sending both is allowed only if they match. Replaying a key returns the first result without executing anything a second time, and sets replayed to true where the response carries that field. Sending the same key with different parameters is refused with 409 IDEMPOTENCY_KEY_REUSED — use a new key for a different request. While the first call is still running, a second call with the same key answers 409 IDEMPOTENT_REQUEST_IN_PROGRESS. A key is remembered for 24 hours from the first call; after that it is forgotten and reusing it starts a new request.
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
The asset and chain to issue your deposit address for.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/partner/v1/crypto-deposit-addresses" \ -H "Content-Type: application/json" \ -d '{ "asset": "USDC", "chain": "ARBITRUM", "idempotencyKey": "acme-crypto-address-0001" }'{ "data": { "accountId": "7e2a0c53-4d81-49b6-8f37-1a5c9e0b2d74", "address": "0x5c1f0a2b3d4e5f60718293a4b5c6d7e8f9012345", "addressId": "9d2c6a4e-73b8-4e8b-a35c-4692b0f11d70", "asset": "USDC", "chain": "ARBITRUM", "createdAt": "2026-09-02T10:15:30.000Z", "disclosure": { "items": [ "ENVIRONMENT_IS_TESTNET: The environment is a testnet (Arbitrum Sepolia). No mainnet deployment exists.", "YIELD_IS_SIMULATED: The vault rate is set administratively and the interest it produces is minted as fresh underlying, not earned. It does not represent a return generated by deployed capital.", "FIAT_RAILS_ARE_MOCKED: No real fiat movement occurs. Balances are ledger entries against a sandbox provider.", "CONVERSION_RATES_ARE_MARKET_QUOTED_OR_REFUSED: A conversion is priced only by an external venue that quotes independently of TCB. When no such venue can price the pair, the conversion is refused rather than priced from an internal table. Read rate.pricingModel on every conversion: MARKET is a venue quote; any other value is not a market rate and must not be presented as one.", "CONTRACTS_ARE_UNAUDITED: No audit has been performed. Mainnet is gated on a two-firm audit that has not been commissioned.", "CUSTODY_IS_TCB_SUBACCOUNT: Everything held for the client — its vault shares, and the tcbUSD it holds between the steps of the tokenised deposit chain — is held in TCB custody, in the one TCB wallet assigned to the client. The client holds no keys and moves those tokens only through this API; each sub-account's shares and tcbUSD are book entries against what that wallet holds.", "INTEGRATION_AGREEMENT_ONLY: Fees as published on the rate card; no yield share, no return commitment." ], "summary": "This is a pilot integration on a testnet. Nothing in this system earns anything: the yield is simulated and the fiat rails are mocked.", "version": "2026-10-27" } }, "success": true, "timestamp": "2026-09-02T10:15:30.000Z"}Fetch one tcbUSD redemption GET
The redemption in its current state.
List crypto deposits GET
Every recorded arrival at your deposit addresses, newest first — credited deposits and FAILED records alike. A deposit appears here the moment it is recorded; there is no POST, because a crypto deposit is initiated on-chain and the transfer itself is the request.