Developers · API Reference
Four transports, one model.
REST for state, WebSocket for streams, FIX for institutional flow, webhooks for events you should not have to poll for. All of them describe the same objects.
- What it is
- Reference material for every transport the platform exposes.
- Who it is for
- Developers writing integrations, trading tools or internal dashboards.
- Why it matters
- Consistency across transports means you learn the model once.
- How it connects
- Every transport passes the same authentication, permission and risk checks as the interface.
- What happens next
- Get sandbox keys and make a call.
What is inside
01
REST
Versioned JSON over HTTPS with documented rate limits and error shapes.
02
WebSocket
Subscribe to prices, orders, positions and account events with heartbeats.
03
FIX
Session configuration, supported messages and execution reporting.
04
Webhooks
Signed payloads, retry schedule, replay and idempotency keys.
05
Errors
One error shape across transports, with machine-readable reason codes.
06
Rate limits
Per-key limits published in response headers.
Try it against the sandbox
Sandbox keys are scoped, free and run against simulated data.