/polymarket/markets/book

POST /api/polymarket/markets/book

Price: 1 credit

Get the live order book snapshot for a Polymarket outcome token

How to use it

Get the current order book (market depth) snapshot for one Polymarket outcome token, identified by its clob token id (obtained from a market's outcomes via the markets endpoint). Returns the full ladder of resting bids and asks (each a price/size level), the derived best bid, best ask, spread and midpoint, the last trade price, tick size, minimum order size, and the snapshot timestamp. This is a point-in-time snapshot of resting liquidity, not a price history.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• token_id string required — Outcome token id (clob token id of one market outcome) (examples: "21742633143463906290569050155826241533067272736897614950488156847949938836455"; minLength: 1)

Response

• @type string (default: "PolymarketOrderBook")
• token_id string required
• condition_id string nullable
• hash string nullable
• bids array (default: [])
  • @type string (default: "PolymarketOrderLevel")
  • price number required
  • size number required
• asks array (default: [])
  • @type string (default: "PolymarketOrderLevel")
  • price number required
  • size number required
• best_bid number nullable
• best_ask number nullable
• spread number nullable
• midpoint number nullable
• last_trade_price number nullable
• tick_size number nullable
• min_order_size number nullable
• neg_risk boolean nullable
• updated_at integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Order book not found (token id is unknown or the market has no live order book) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.