Binary Order Entry
The binary order-entry surface is designed for low-overhead submission and deterministic acknowledgement.
Message types
| Type | Purpose |
|---|---|
NewOrder | Submit a single order |
CancelOrder | Cancel by client order id |
ReplaceOrder | Atomically amend price, quantity, or flags |
BulkOrder | Refresh many quotes in one message |
MassCancel | Cancel by account, market, or side |
Heartbeat | Keep session alive |
NewOrder fields
| Field | Notes |
|---|---|
client_order_id | Idempotency key, equivalent to FIX ClOrdID |
market_id | Numeric market identifier negotiated at session start |
side | Buy or sell |
order_type | Limit, market, conditional, or algo extension |
time_in_force | GTC, IOC, FOK, post-only extension |
price | Fixed-scale integer, omitted for market orders |
quantity | Fixed-scale integer |
flags | Reduce-only, post-only, STP policy |
Acknowledgement model
Ack confirms gateway acceptance. ExecReport confirms sequencer-visible order
state. Clients should not treat gateway acknowledgement as a fill or final order
state.
Failure model
Rejects use stable numeric reason codes that map to the public Error Model: tick-size violation, insufficient collateral, stale nonce, duplicate client order id, and account permission failures.