Create transfer
Create a new transfer to move funds from a source to a target.
All transfers first transition to quoted. If execute: false, the transfer stays quoted until you call /v2/transfers/{transferId}/execute.
If execute: true, quoted status emits momentarily before the transfer moves to processing, where execution proceeds. Subscribe to the transfers webhook to follow progress in real time instead of polling.
Authorizations
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
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 - 128Body
A request to create a transfer.
Specifies whether the given amount is to be received by the target or taken from the source.
target: The transfertargetreceives the exact value specified inamount. Fees are added to the amount taken from the transfersource.source: The transfertargetreceives the value specified inamount, minus any fees.
target, source "source"
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.
false
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.
Response
Successfully created 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.
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.
A point-in-time snapshot of estimated values for a transfer where exact amounts cannot be locked in at quote time (e.g., when the executed rate is determined at execution time and moves with the market).
Present in both pre-execution and post-execution states:
-
Quoted state: top-level fields whose values cannot be guaranteed are absent;
estimateholds their estimated values. -
Completed state: top-level fields contain the actual executed values;
estimateis retained as an immutable audit snapshot of the pre-execution estimate.
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.