Skip to main content
Package: com.coinbase.cdp.resources.depositdestinations

​
Method Details

​
listDepositDestinations

Overload 1
List deposit destinations. You can optionally filter the results by type, account ID, network, or cryptocurrency address. Results are sorted by creation date in descending order (newest first). Returns: CdpClientHttpResponse<ListDepositDestinationsResponse> Overload 2
List deposit destinations. You can optionally filter the results by type, account ID, network, or cryptocurrency address. Results are sorted by creation date in descending order (newest first). Parameters: request - ListDepositDestinationsRequest Returns: CdpClientHttpResponse<ListDepositDestinationsResponse> Overload 3
List deposit destinations. You can optionally filter the results by type, account ID, network, or cryptocurrency address. Results are sorted by creation date in descending order (newest first). Parameters: requestOptions - RequestOptions Returns: CdpClientHttpResponse<ListDepositDestinationsResponse> Overload 4
List deposit destinations. You can optionally filter the results by type, account ID, network, or cryptocurrency address. Results are sorted by creation date in descending order (newest first). Parameters: request - ListDepositDestinationsRequest requestOptions - RequestOptions Returns: CdpClientHttpResponse<ListDepositDestinationsResponse>

​
createDepositDestination

Overload 1
Create a new deposit destination for an account. Two types are supported: crypto (public): provisions a cryptocurrency address on the requested network. The returned crypto.address is the deposit address; funds sent to it are credited to the target account in the specified asset. For Customer-owned accounts, the Customer must have the custodyCrypto and custodyStablecoin capabilities enabled. fiat (private-beta): provisions a bank account at a CDP banking partner. The server picks the account type (e.g. us_bank) and supported payment rails based on the account’s eligibility; pass fiat.paymentRail to influence partner selection. The returned fiat object contains the bank account details the depositor needs to send funds. For Customer-owned accounts, the Customer must have the custodyFiat capability enabled. Requires account enablement — contact your Coinbase representative for access. Fields and behavior may change before general availability. For Customer-owned accounts not authorized for the required capabilities, the request is rejected with customer_not_authorized (HTTP 403). The created destination’s status starts as pending for fiat (it becomes active once the partner provisioning callback completes) and active for crypto. Parameters: request - CreateDepositDestinationBody Returns: CdpClientHttpResponse<DepositDestination> Overload 2
Create a new deposit destination for an account. Two types are supported: crypto (public): provisions a cryptocurrency address on the requested network. The returned crypto.address is the deposit address; funds sent to it are credited to the target account in the specified asset. For Customer-owned accounts, the Customer must have the custodyCrypto and custodyStablecoin capabilities enabled. fiat (private-beta): provisions a bank account at a CDP banking partner. The server picks the account type (e.g. us_bank) and supported payment rails based on the account’s eligibility; pass fiat.paymentRail to influence partner selection. The returned fiat object contains the bank account details the depositor needs to send funds. For Customer-owned accounts, the Customer must have the custodyFiat capability enabled. Requires account enablement — contact your Coinbase representative for access. Fields and behavior may change before general availability. For Customer-owned accounts not authorized for the required capabilities, the request is rejected with customer_not_authorized (HTTP 403). The created destination’s status starts as pending for fiat (it becomes active once the partner provisioning callback completes) and active for crypto. Parameters: body - CreateDepositDestinationRequest Returns: CdpClientHttpResponse<DepositDestination> Overload 3
Create a new deposit destination for an account. Two types are supported: crypto (public): provisions a cryptocurrency address on the requested network. The returned crypto.address is the deposit address; funds sent to it are credited to the target account in the specified asset. For Customer-owned accounts, the Customer must have the custodyCrypto and custodyStablecoin capabilities enabled. fiat (private-beta): provisions a bank account at a CDP banking partner. The server picks the account type (e.g. us_bank) and supported payment rails based on the account’s eligibility; pass fiat.paymentRail to influence partner selection. The returned fiat object contains the bank account details the depositor needs to send funds. For Customer-owned accounts, the Customer must have the custodyFiat capability enabled. Requires account enablement — contact your Coinbase representative for access. Fields and behavior may change before general availability. For Customer-owned accounts not authorized for the required capabilities, the request is rejected with customer_not_authorized (HTTP 403). The created destination’s status starts as pending for fiat (it becomes active once the partner provisioning callback completes) and active for crypto. Parameters: request - CreateDepositDestinationBody requestOptions - RequestOptions Returns: CdpClientHttpResponse<DepositDestination> Overload 4
Create a new deposit destination for an account. Two types are supported: crypto (public): provisions a cryptocurrency address on the requested network. The returned crypto.address is the deposit address; funds sent to it are credited to the target account in the specified asset. For Customer-owned accounts, the Customer must have the custodyCrypto and custodyStablecoin capabilities enabled. fiat (private-beta): provisions a bank account at a CDP banking partner. The server picks the account type (e.g. us_bank) and supported payment rails based on the account’s eligibility; pass fiat.paymentRail to influence partner selection. The returned fiat object contains the bank account details the depositor needs to send funds. For Customer-owned accounts, the Customer must have the custodyFiat capability enabled. Requires account enablement — contact your Coinbase representative for access. Fields and behavior may change before general availability. For Customer-owned accounts not authorized for the required capabilities, the request is rejected with customer_not_authorized (HTTP 403). The created destination’s status starts as pending for fiat (it becomes active once the partner provisioning callback completes) and active for crypto. Parameters: body - CreateDepositDestinationRequest requestOptions - RequestOptions Returns: CdpClientHttpResponse<DepositDestination>

​
getDepositDestinationById

Overload 1
Get a specific deposit destination by its ID. Parameters: depositDestinationId - DepositDestinationId Returns: CdpClientHttpResponse<DepositDestination> Overload 2
Get a specific deposit destination by its ID. Parameters: depositDestinationId - DepositDestinationId request - GetDepositDestinationByIdRequest Returns: CdpClientHttpResponse<DepositDestination> Overload 3
Get a specific deposit destination by its ID. Parameters: depositDestinationId - DepositDestinationId requestOptions - RequestOptions Returns: CdpClientHttpResponse<DepositDestination> Overload 4
Get a specific deposit destination by its ID. Parameters: depositDestinationId - DepositDestinationId request - GetDepositDestinationByIdRequest requestOptions - RequestOptions Returns: CdpClientHttpResponse<DepositDestination>