POST /api/polymarket/markets/history
Price: 5 credits
Get the price (probability) history of a market outcome token
Get the historical price curve of one market outcome token (the probability over time of that outcome). Identify the token by its outcome token id, which you can read from the clob_token_ids of a market. Choose a time window with interval (1h/6h/1d/1w/1m/max) and optionally fidelity (minutes per point). Returns points with date_at (unix seconds) and price, oldest first. For long-running or resolved markets, raise fidelity to retrieve the down-sampled history.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)token_id string required — Outcome token id of the market (one side of the outcome) (examples: "21742633143463906290569050155826241533067272736897614950488156847949938836455"; minLength: 1)interval string — Time window of the price curve: 1h, 6h, 1d, 1w, 1m, or max (default: "max"; one of: "1h", "6h", "1d", "1w", "1m", "max")fidelity integer nullable — Resolution of the curve in minutes per point. Higher values return coarser, longer-reaching history; required by the 1w and 1m intervals (min: 1)count integer required — Maximum number of price points to return (min: 1)@type string (default: "PolymarketPricePoint")date_at integer requiredprice number nullable422 — 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 — No price history available for this token 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.