Developers · Documentation
Concepts before endpoints.
The endpoints are easy. What matters is the model: how an instrument is described, how a permission is evaluated, when an order is validated, and what an event guarantees.
- What it is
- Conceptual and task-based documentation for the Raptor API and platform.
- Who it is for
- Developers integrating with or building on top of Raptor.
- Why it matters
- Most integration bugs come from a misunderstood model, not a mistyped endpoint.
- How it connects
- Documentation references the same instrument and permission models the platform enforces.
- What happens next
- Read the concepts, then request sandbox keys.
What is inside
01
Authentication
API keys, scopes, rotation and what each scope permits.
02
Instruments
Symbology, tick and contract size, margin profile and session definitions.
03
Market data
Snapshot and streaming access, and what staleness looks like.
04
Orders
Order types, validation order, refusal reasons and idempotency.
05
Positions and accounts
Position keeping, P&L calculation basis and account state.
06
Events and webhooks
Delivery guarantees, signing, retry behaviour and replay.
Something unclear?
Documentation gaps are bugs. Send them to developers@777raptor.com and they get fixed.