Transfers (V2)
Move funds between fiat and stablecoins for your Customers.
A transfer moves funds from a Customer to a recipient.
Transfers (V2) replaces the deprecated Transfers (V1).
| Action | Endpoint |
|---|---|
| Create a quote | POST /api/v2/transfers/quotes |
| Get the transfer requirements | GET /api/v2/transfers/quotes/{quote_id}/requirements |
| Create a transfer | POST /api/v2/transfers |
| Retrieve a transfer | GET /api/v2/transfers/{transfer_uuid} |
| List all transfers | GET /api/v2/transfers |
With this API, you can:
- On-Ramp: convert fiat to stablecoins, such as USD to USDC.
- Off-Ramp: convert stablecoins to fiat, such as USDC to MXN.
- On-Chain: move stablecoins between wallets or blockchains, such as USDC from Ethereum to Polygon.
How It Works
Every transfer starts with a quote. The quote locks the exchange rate and fees until it expires, so the transfer uses the same values you showed your Customer.
You also use the quote id to get the transfer requirements: the fields the transfer needs, such as the recipient's bank details. They're different for each country, currency and payment method.
A transfer takes three steps:
Then follow its status by retrieving it, or with Webhooks. See Transfer Lifecycle.
List and Filter Transfers
GET /api/v2/transfers returns your transfers, 15 per page. Use page to get the next pages. The page size can't be changed.
Add these query parameters to filter the list. They are all optional and you can combine them:
| Filter | Value |
|---|---|
status | A transfer status, such as completed or pending_harbor. |
type | on-ramp, off-ramp or swap. |
created_from, created_to | A date in YYYY-MM-DD format. |
application_transfer_uuid | The ID you set when you created the transfer. It must match exactly. |
on_behalf_of | A Customer's cus_ ID, to get only that Customer's transfers. |
Add a filter to the URL after ?, and join several with &.
Get only the completed transfers:
curl --location 'https://harbor-sandbox.owlpay.com/api/v2/transfers?status=completed' \
--header 'X-API-KEY: {YOUR_API_KEY}'Find a transfer by your own ID. It is also in every transfer response and webhook event, next to Harbor's own uuid:
curl --location 'https://harbor-sandbox.owlpay.com/api/v2/transfers?application_transfer_uuid=sp_tx_123456' \
--header 'X-API-KEY: {YOUR_API_KEY}'Get one Customer's transfers:
curl --location 'https://harbor-sandbox.owlpay.com/api/v2/transfers?on_behalf_of={customer_uuid}' \
--header 'X-API-KEY: {YOUR_API_KEY}'Combine filters, for example the completed on-ramp transfers created in November:
curl --location 'https://harbor-sandbox.owlpay.com/api/v2/transfers?type=on-ramp&status=completed&created_from=2026-11-01&created_to=2026-11-30' \
--header 'X-API-KEY: {YOUR_API_KEY}'Get the next page. The filters stay the same:
curl --location 'https://harbor-sandbox.owlpay.com/api/v2/transfers?status=completed&page=2' \
--header 'X-API-KEY: {YOUR_API_KEY}'More in This Section
- Transfer Purpose: a required field in
destinationthat states the reason for the transfer, for compliance purposes. - Recipients: save a beneficiary's details and reuse them.
- Transfer to Local Currency: pay recipients in their own currency, through local payment networks.
- Pay First, Bind Later: start a debit card payout before you have the card details.
- Transfer Limits: the limits on your Customers' transfers.
- Transfer RFI: when a transfer needs more information.
- Supporting Documents: upload a Customer's documents ahead of time and attach them to transfers.
To fund an on-ramp from a linked bank account (ACH Pull), see Link Bank Account.
Updated about 14 hours ago