Create Transfer
Initiate a transfer. The request is a Bridge-style source / destination pair; only four pairings are accepted:
usd/ach_push→usdc/ethereum— bank onrampusdc/ethereum→usd/ach— wallet offrampusdc/ethereum→c0/ethereum— deposit into C0c0/ethereum→usdc/ethereum— withdraw from C0
Crypto sources must be one of your organization’s wallets (GET /v1/wallets); supply from_address. Bank sources/destinations supply the bank_account.id via external_account_id. Fiat legs route through Bridge.xyz; the USDC↔C0 pairings execute on-chain. The response is the same unified Transfer shape returned by GET /v1/transfers.
Authorizations
API key for authentication. Pass your key in the x-api-key header.
Headers
Caller-chosen string (≤256 chars) that uniquely identifies this request. Resending the same key replays the original response; reusing the same key with a different body returns 422. Keys are scoped per organization.
1 - 256Body
Bridge-style transfer request. The (source.currency / source.payment_rail) → (destination.currency / destination.payment_rail) tuple selects the backend; only four pairings are valid.
Response
Transfer created
A transfer initiated by the organization. Covers wallet→wallet (on-chain), bank→wallet (Bridge onramp), and wallet→bank (Bridge offramp) under one unified shape. Each row has a symmetric from and to side.
Camino-owned UUID.
One side of a transfer. Exactly one of address (wallet) or bankAccount (bank) is populated.
One side of a transfer. Exactly one of address (wallet) or bankAccount (bank) is populated.
pending, submitted, completed, failed On-chain hash once the wallet-side leg (if any) has been submitted; null otherwise.