Skip to main content
POST
/
v2
/
transfers
/
{transferId}
/
execute
Execute a transfer
curl --request POST \
  --url https://api.cdp.coinbase.com/platform/v2/transfers/{transferId}/execute \
  --header 'Authorization: Bearer <token>'
{
  "transferId": "transfer_af2937b0-9846-4fe7-bfe9-ccc22d935114",
  "status": "processing",
  "source": {
    "accountId": "account_af2937b0-9846-4fe7-bfe9-ccc22d935114",
    "asset": "usd"
  },
  "target": {
    "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "network": "base",
    "asset": "usdc"
  },
  "amount": "100.00",
  "asset": "usd",
  "sourceAmount": "103.50",
  "sourceAsset": "usd",
  "targetAmount": "100.00",
  "targetAsset": "usdc",
  "exchangeRate": {
    "sourceAsset": "usd",
    "targetAsset": "usdc",
    "rate": "1"
  },
  "fees": [
    {
      "type": "bank",
      "amount": "2.50",
      "asset": "usd"
    },
    {
      "type": "conversion",
      "amount": "1.00",
      "asset": "usd"
    }
  ],
  "executedAt": "2023-10-08T14:31:00Z",
  "createdAt": "2023-10-08T14:30:00Z",
  "updatedAt": "2023-10-08T14:31:00Z",
  "validateOnly": false,
  "metadata": {
    "invoiceId": "12345",
    "reference": "Payment for invoice #12345"
  }
}

Authorizations

​
Authorization
string
header
required

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.

Headers

​
X-Idempotency-Key
string

An optional UUID v4 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.

Required string length: 36

Path Parameters

​
transferId
string
required

The ID of the transfer.

Response

Successfully committed a transfer.

A Transfer represents all the information needed to execute a transfer and tracks the lifecycle of a transfer from initiation through completion or failure.

​
source
Account · object
required

The source of the transfer.

Example:
{
  "accountId": "account_af2937b0-9846-4fe7-bfe9-ccc22d935114",
  "asset": "usd"
}
​
target
Account · object
required

The target of the transfer.

Example:
{
  "accountId": "account_af2937b0-9846-4fe7-bfe9-ccc22d935114",
  "asset": "usd"
}
​
transferId
string

The ID of the transfer. Required when validateOnly is false.

Example:

"transfer_af2937b0-9846-4fe7-bfe9-ccc22d935114"

​
status
enum<string>

The current status of the transfer, indicating what action you need to take next. Required when validateOnly is false.

Available options:
quoted,
processing,
completed,
failed
Example:

"quoted"

​
sourceAmount
string

The amount of the source asset that will be transferred out in atomic units.

Example:

"103.50"

​
sourceAsset
string

The asset symbol of the source amount.

Required string length: 1 - 42
Example:

"usdc"

​
targetAmount
string

The amount of the target asset that will be transferred in atomic units.

Example:

"100.00"

​
targetAsset
string

The asset symbol of the target amount.

Required string length: 1 - 42
Example:

"btc"

​
exchangeRate
object

Exchange rate information for currency conversion. The rate indicates how much of the target asset is equivalent to one unit of the source asset.

Example:
{
  "sourceAsset": "usdc",
  "targetAsset": "btc",
  "rate": "0.00001"
}
​
fees
object[]

The fees associated with this transfer. Different transfer types have different fee structures.

NOTE: These examples are not exhaustive.

Common examples:

  • Crypto transfers: Network fees (gas) paid in the native token
  • Fiat conversions: Processing fees + exchange fees in USD
  • Wire transfers: Wire fees ($15) + processing fees ($5) in USD
  • Crypto conversions: Spread fees paid in the source asset.
Example:
[
  {
    "type": "bank",
    "amount": "20",
    "asset": "usd"
  },
  {
    "type": "conversion",
    "amount": "1.00",
    "asset": "usdc"
  },
  {
    "type": "network",
    "amount": "0.03",
    "asset": "eth"
  }
]
​
completedAt
string<date-time>

The date and time the transfer was completed.

Example:

"2025-01-01T00:05:00Z"

​
failureReason
string

The reason for failure, if the transfer failed. Only present when status is failed.

Example:

"Insufficient balance to complete this transfer."

​
lastError
object

Detailed information about the last error that occurred while processing this transfer. Only present when status is failed.

Example:
{
  "code": "insufficient_funds",
  "message": "The source account does not have sufficient funds for this transfer.",
  "param": "source.accountId",
  "details": {
    "availableBalance": "50.00",
    "requiredAmount": "100.00"
  }
}
​
expiresAt
string<date-time>

The date and time when this transfer will expire if not executed. Only present for quoted status. A new transfer must be created to obtain an updated quote after expiration. Required when validateOnly is false.

Example:

"2025-01-01T00:15:00Z"

​
executedAt
string<date-time>

The date and time the transfer was executed and moved to processing. Only present when status has progressed beyond quoted.

Example:

"2025-01-01T00:01:30Z"

​
createdAt
string<date-time>

The date and time the transfer was created. Required when validateOnly is false.

Example:

"2025-01-01T00:00:00Z"

​
updatedAt
string<date-time>

The date and time the transfer was last updated. Required when validateOnly is false.

Example:

"2025-01-01T00:00:00Z"

​
validateOnly
boolean

If true, validates the transfer without initiating it. If the request is valid, a 2xx will be returned. If the request is invalid, a 4xx error will be returned. The response will include an errorType, for e.g. invalid_target if the specified target cannot receive funds.

Example:

false

​
metadata
object

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.

Example:
{
  "customer_id": "cust_12345",
  "order_reference": "order-67890"
}
​
travelRule
object

(Preview, not yet supported) Required Travel Rule fields differ by region. These requirements are determined based on which Coinbase entity the customer has signed the service agreement for.

Example:
{
  "isSelf": false,
  "isIntermediary": true,
  "originator": {
    "name": "John Doe",
    "address": {
      "line1": "123 Main St",
      "line2": "Unit 201",
      "city": "Luxembourg",
      "postCode": "L-1234",
      "countryCode": "LU"
    },
    "financialInstitution": "PayPal, Inc.",
    "vasp": {
      "name": "Fidelity Digital Asset Services, LLC",
      "address": {
        "line1": "123 Market St",
        "line2": "Suite 400",
        "city": "San Francisco",
        "state": "California",
        "postCode": "94105",
        "countryCode": "US"
      },
      "identifier": "5493001KJTIIGC8Y1R17"
    }
  },
  "beneficiary": {
    "name": "Jane Smith",
    "address": {
      "line1": "456 Oak Ave",
      "city": "Paris",
      "postCode": "75001",
      "countryCode": "FR"
    },
    "walletType": "custodial"
  }
}
​
details
object

Additional details about the transfer. For example, if the transfer was sent to a deposit destination, the information about that destination will be included in this field.

Example:
{
  "depositDestination": {
    "id": "depositDestination_af2937b0-9846-4fe7-bfe9-ccc22d935114"
  },
  "onchainTransactions": [
    {
      "transactionHash": "0x363cd3b3d4f49497cf5076150cd709307b90e9fc897fdd623546ea7b9313cecb",
      "network": "ethereum"
    }
  ]
}