Skip to main content
GET
List transfers

What this endpoint does

Lists conversions automatically created when customers fund direct payment routes.

When to use it

Use it for transfer search, reconciliation, and monitoring across customers and routes.

Before you call

Authenticate with an API key that can read this resource. Results are restricted to the tenant account bound to that key.

Money and balance effect

This is a read-only request. It does not reserve, debit, credit, or settle money.

States and completion

The status field carries the enum values shown in the schema, not display copy. Broadly: awaiting_payin, awaiting_deposit, and the deposit_* states are waiting on funds; states such as screening, fx_executed, sweeping, pooled, payout_instructed, and sending are in flight; on_hold, payout_held, and frozen are holds; completed, failed, cancelled, returned, expired, and reversed are terminal. Treat only completed as settled — never infer settlement from creation alone.

Safe retries

GET requests are read-only and may be retried with normal exponential backoff. Do not send an Idempotency-Key. Read Activity and history for the complete workflow.

Authorizations

X-Api-Key
string
header
required

API key for authentication. Generate one from your account settings.

Query Parameters

page
integer

Page number (default: 1)

per_page
integer

Items per page (default: 25, max: 100)

status
enum<string>

Filter by transfer status

Available options:
pending,
confirmed
account_id
string<uuid>

Filter transfers involving this account

start_date
string<date>

Filter transfers from this date

end_date
string<date>

Filter transfers until this date

Response

transfers listed

transfers
object[]
required
pagination
object
required