API overview
Resource boundaries: orders, customers, funds, and statuses.
Open →This page provides structure and examples for integration planning. Access and keys are issued upon request.
Resource boundaries: orders, customers, funds, and statuses.
Open →Key issuance, scopes, and signature examples.
Open →Event list and payload samples (no real endpoints disclosed).
Open →Common error shape and retry guidance.
Open →Compatibility notes and changes.
Open →Operational status and notification (sample).
Open →Order lifecycle: create → verify → settle → reconcile. Example object (not a real endpoint).
{
"id": "ord_01H…",
"type": "onramp",
"status": "pending",
"fiat": { "currency": "USD", "amount": "1000.00" },
"crypto": { "asset": "USDT", "network": "TRON", "amount": "999.10" },
"created_at": "2026-03-31T00:00:00Z"
}
Keys and scopes are managed in the ops console (beta). We recommend environment separation and least privilege.
Authorization: Bearer <api_key>
X-Request-Id: <uuid>
To request access, submit regions/currencies and expected flow via the access form.
Common events: order created, status changed, settlement completed, reconciliation ready.
{
"event": "order.status_changed",
"timestamp": "2026-03-31T00:00:00Z",
"data": {
"order_id": "ord_01H…",
"from": "pending",
"to": "settled"
}
}
A consistent error object for alerting and debugging. Idempotency keys are supported in beta.
{
"error": {
"code": "rate_limited",
"message": "Too many requests",
"retry_after_ms": 1200
}
}
Added callback samples and error shapes; refined private beta access flow.
Updated console permission model draft and export guidance.
Initialized documentation skeleton (private beta).
Current: Operational (sample). Email notifications available in beta.
Last 30 days: 99.9% uptime (example)
Incidents: 0