Crypto trading API. Connect your execution workflow.
Automate spot orders, OTC conversion and account operations, with signed callbacks that keep your systems informed.
Trading workflow
Conceptual sequence
- account access
1. Establish credentials and permissions.
Use the authentication described in the Client API reference.
- order request
2. Submit a supported spot order.
Follow the documented request fields and account requirements.
- order lifecycle
3. Track status and available actions.
Review open orders and supported cancellation behaviour.
- trade history
4. Bring fills back to your systems.
Use documented account and trade records, plus signed Client API callbacks, to keep your systems current.
Build against the reference. Operate against clear limits.
The official documentation defines supported endpoints and fields. Confirm the access, order types and operating limits that apply before sending live activity.
| Integration decision | Confirm with your team |
|---|---|
| Permissions | Which account actions the credentials should allow |
| Order handling | Accepted requests, status handling and cancellation |
| Resilience | Timeouts, retries and reconciliation behaviour |
| Controls | Testing, key handling and production access |
More of the account. Within the same integration.
Connect supported OTC quotes and conversion, Virtual Wallets, Earn subscriptions and withdrawal batches. Fiat funding and withdrawal fee-preview functions help finance plan the movement.
Before production access.
Details for your next decision.
-
What can we automate beyond spot orders?
The Client API supports OTC quote and conversion, Virtual Wallet operations, eligible Earn subscriptions, withdrawal batches and supported fiat funding operations. Access and product permissions apply.
-
How are requests and callbacks secured?
Authenticated Client API requests use a key, secret and HMAC signing. The API also supports signed outbound callbacks to your configured URL and callback retry functions.
-
Is a test environment available?
Non-production Client API facilities include an HMAC-signature helper for integration testing. Arrange access with XBO; that helper is disabled in production. This does not promise a simulated trading sandbox for every product.
-
Can we manage deposits and withdrawals?
Supported funding functions include balances, crypto deposit addresses and withdrawals, fiat transfer instructions and withdrawal fee previews. Review the requirements for each asset, route and account.
-
What rate limits apply?
Use the limits applicable to the interface and account, and design request volumes, retries and reconciliation accordingly. The current reference and onboarding define the relevant limits.
Explore what else your business can do with crypto.
Explore the services that work alongside this one.
Bring your trading workflow closer to the market.
Explore the Client API documentation and discuss the connection your desk needs.