POST /orders-v3 with timeInForce: "IOC" or "FOK", and the order
executes against the book immediately instead of resting on it.
timeInForce is the one field that makes you a taker. You sign the same struct a maker signs, in
your own frame.
Prerequisites
Same as posting: your proxy must be deployed and funded, and auth is an API key plus your signature. See Prerequisites on Posting orders.The price you submit
percentageOdds is the highest implied probability you’re willing to pay — you match at that price or
better, never worse.
percentageOdds is an implied probability, so a lower number is a bigger payout: submitting
"48000000000000000000" (48%) matches you at 46% but never at 50%.
Steps
- Read the book in your frame —
GET /orderbook-v3/snapshotwithshowTakerPerspective=true, optionally, to avoid doing the conversion yourself. - Pick the best level for the outcome you want.
- Sign and submit an
IOCorFOKat that level’s price. It matches at that price or better, or not at all. - Read the result from your trades and fills — an
IOC/FOKnever rests. - Or listen on your account streams — subscribe to
account:fills_v3_#{address},account:trades_v3_#{address}, oraccount:orders_v3_#{address}to have the same updates pushed to you instead of polling.
Taking an IOC end to end
201 with the order id and status PENDING. An IOC never rests, so read the
result from your trades and fills, not from GET /orders-v3. Join
GET /fills-v3 rows on fill.orderId.
Partial fills
IOC discards whatever didn’t match; FOK cancels entirely rather than executing partially — see
Time in force for the full behavior table.
An IOC that fills partially still reports inactiveReason: "NO_LIQUIDITY" on the order. That reason
describes the discarded remainder. A FOK checks
fillable depth first and cancels entirely if the depth can’t cover your size.
Related
Posting orders
The same signing and submission path, from the maker’s side.
Market making
The global notional budget aggressive orders are checked against.
Time in force
Why IOC and FOK are the only two immediate types.
Create orders
Fields, validation rules and every error body.
Get orderbook snapshot
Reading depth, and the prices from the taker’s side.
Bet lifecycle
What happens to a bet after it matches.