/polymarket/markets/trades

POST /api/polymarket/markets/trades

Price: 1 credit

Get the public trade feed for a Polymarket market by its condition id

How to use it

Get the public stream of executed trades for a Polymarket prediction market, identified by its on-chain condition id. Each trade carries the side (buy or sell), price, amount of shares, the outcome traded (e.g. Yes or No), the trader's wallet and public profile, the originating transaction hash, and the trade time. Optionally filter to one side or to a single trader wallet.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• market string required — On-chain condition id of the market (0x-prefixed 64-hex) (examples: "0xdd22472e552920b8438158ea7238bfadfa4f736aa4cee91a6b86c39ead110917"; pattern: ^0x[0-9a-fA-F]{64}$)
• count integer required — Max number of trades to return (min: 1)
• side string nullable — Only return trades on this side (one of: "BUY", "SELL")
• user string nullable — Only return trades made by this trader wallet (0x… address) (examples: "0xd53d94afcb32eb1db663118e5f830b48d83808ee")

Response

• @type string (default: "PolymarketTrade")
• transaction_hash string required
• condition_id string nullable
• asset_id string nullable
• side string nullable
• price number nullable
• amount number nullable
• outcome string nullable
• outcome_index integer nullable
• alias string nullable
• event_alias string nullable
• image string nullable
• trader object nullable
  • @type string (default: "PolymarketTradeTrader")
  • wallet string required
  • name string nullable
  • pseudonym string nullable
  • bio string nullable
  • image string nullable
• traded_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 — The entity was not found, or a precondition failed 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.