Base URL
Authentication
All requests require an API key in theAuthorization header:
Request format
- Request bodies use
Content-Type: application/json - All monetary amounts are strings (e.g.,
"500.00") to avoid floating-point precision issues - Dates use ISO 8601 format (
2026-02-14T10:30:00Z) - IDs are prefixed strings (e.g.,
pay_,ben_,bat_)
Response format
All successful responses are wrapped in adata envelope:
Single resource
List response
Idempotency
POST requests support idempotency via theIdempotency-Key header. See Idempotency for details.
Rate limiting
Requests are rate-limited per IP. Exceeding the limit returns429 Too Many Requests with a Retry-After header.
Resource overview
| Resource | Endpoint | Description |
|---|---|---|
| Payouts | /v1/payouts | Create and manage money movements |
| Beneficiaries | /v1/beneficiaries | Manage payout recipients |
| Instruments | /v1/instruments | Payment methods for beneficiaries |
| Balances | /v1/balances | Check your funded account balances |
| Quotes | /v1/quotes | Get FX quotes for cross-currency payouts |
| Batches | /v1/batches | Bulk payout uploads via CSV |
| Webhooks | /v1/webhooks | Real-time event notifications |
| API Keys | /v1/api-keys | Manage your API credentials |
| Onboarding | /v1/onboarding | Merchant application and registration |
| Documents | /v1/documents | KYB document management |
| Corridors | /v1/corridors | Available payment corridors |