GTC orders on the book and managing what happens to them — earning the
spread between the price you post and what a taker receives. The mechanics of posting are on
Posting orders.
Prerequisites
Your proxy must be deployed and funded before
POST /orders-v3 accepts anything.Minimal example
GET /metadata/obv3— once, at startup.GET /markets/active— discover the markets you cover.GET /orderbook-v3/snapshot— read the aggregated levels and the book’s version.- Price — your model’s output, snapped to the ladder.
POST /orders-v3— up to 10 orders per request.- Watch —
account:orders_v3_#{address}for order state,account:fills_v3_#{address}for fills (joined onorderId),orderbook_v3:{marketHash}for the book moving. - Reprice —
DELETE /orders-v3by id, thenPOSTthe replacement.
Related
Posting orders
Fields, signing, and the validation rules on create.
Cancelling orders
Picking a cancel route, and confirming before you exit.
Tracking your orders
The order row in full, and why a missing order has more than one explanation.
Odds rounding
Rounding a model price onto the odds ladder.
Market making parlays
Quoting parlay requests, where
FOK is required.