Skip to main content
The order book shows all open buy (bid) and sell (ask) orders for a market outcome, aggregated by price level. Use it to understand where the market is trading and to pick a good price for a limit order.
All examples use https://api.futuur.com/v2.0. The order book endpoint does not require authentication.

What the order book shows

The order book aggregates open orders at each price level into two sides:
  • Bids (bid in the response) — buyers willing to pay up to a certain price (buy orders)
  • Asks (ask in the response) — sellers willing to accept at least a certain price (sell orders)
Each level shows the quantity available and the cumulative depth of the book up to that price. This tells you how much liquidity exists and at what prices.

Fetching the order book

Call GET /markets/{id}/book/ with the required currency_mode parameter and the market ID in the path.

Required parameters

Optional parameters

Example response

Order book fields

Each level in the bid and ask arrays contains the following fields: For bids, levels are sorted from highest price to lowest (best bid first). For asks, levels are sorted from lowest price to highest (best ask first).

Interpreting the best bid and ask

The best bid is the first entry in the bid array — the highest price a buyer is currently willing to pay. The best ask is the first entry in ask — the lowest price a seller will accept.
python
For the example response above:
  • Best bid: 0.62
  • Best ask: 0.65
  • Spread: 0.03 (3 cents per share)
  • Mid price: 0.635
A narrow spread indicates high liquidity. A wide spread means fewer active traders and more price uncertainty.
The mid-price is a useful reference point. Placing a limit order just inside the spread — for example, a bid at 0.63 — can get you a better fill price than a market order at the best ask of 0.65.

Using the order book to pick a limit price

The cumulative_shares field tells you how much total liquidity is available up to a given price. Use this to estimate how many shares you can buy or sell at a target price.
python
For the example response:
  • Buying 300 shares: best ask at 0.65 covers it (cumulative_shares = 300)
  • Buying 1000 shares: requires depth up to 0.67 (cumulative_shares = 1050)
Setting your limit price at 0.67 or placing a market order would fill a 1000-share buy in this scenario.
Liquidity changes continuously. The order book snapshot you fetch may be stale by the time your order executes. For large orders, consider splitting into smaller chunks.

Long vs short order books

The position parameter controls which order book you’re viewing: Long and short positions trade in separate books. If you hold a short position and want to sell, fetch the short order book (position=short) to see relevant bids.
python

Realtime order-book updates

Subscribe to the per-event Pusher channel event-{event_id} and listen for order-book-update. That event carries absolute top-N bid/ask levels for the affected market — apply them directly for top-of-book quoting. Full-depth snapshots are not streamed over Pusher. When you need depth beyond top-N, call the REST order book endpoint. See Channels and events for the payload.