/polymarket/events

POST /api/polymarket/events

Price: 5 credits

Get a Polymarket event by its id or slug

How to use it

Get a single Polymarket event (the umbrella that groups several related prediction markets, e.g. an election or tournament) by its numeric id or slug. Returns the event title, alias, description, category tags, lifecycle flags (active, closed, archived), aggregate trading volume (total and per window), liquidity, open interest, comment count, start/end/created/updated timestamps, and the full list of nested markets — each with its question, outcomes, prices, clob token ids and volumes. Use the markets endpoint to fetch one contract directly.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• event string required — Event id (numeric) or slug (examples: "903193", "presidential-election-winner-2024"; minLength: 1)

Response

• @type string (default: "PolymarketEvent")
• id string required
• alias string nullable
• ticker string nullable
• description string nullable
• image string nullable
• icon string nullable
• tags array (default: [])
  • @type string (default: "PolymarketEventTag")
  • id string required
  • label string nullable
  • alias string nullable
• markets array (default: [])
  • @type string (default: "PolymarketMarket")
  • id string required
  • alias string nullable
  • question string required
  • description string nullable
  • condition_id string nullable
  • question_id string nullable
  • image string nullable
  • icon string nullable
  • outcomes array (default: [])
    • @type string (default: "PolymarketMarketOutcome")
    • outcome string required
    • price number nullable
    • clob_token_id string nullable
  • clob_token_ids array (default: [])
  • best_bid number nullable
  • best_ask number nullable
  • spread number nullable
  • last_trade_price number nullable
  • one_hour_price_change number nullable
  • one_day_price_change number nullable
  • one_week_price_change number nullable
  • one_month_price_change number nullable
  • one_year_price_change number nullable
  • volume number nullable
  • volume_24hr number nullable
  • volume_1wk number nullable
  • volume_1mo number nullable
  • volume_1yr number nullable
  • liquidity number nullable
  • competitive number nullable
  • order_min_size number nullable
  • order_price_min_tick_size number nullable
  • is_active boolean nullable
  • is_closed boolean nullable
  • is_archived boolean nullable
  • is_new boolean nullable
  • is_featured boolean nullable
  • is_restricted boolean nullable
  • accepting_orders boolean nullable
  • enable_order_book boolean nullable
  • neg_risk boolean nullable
  • market_type string nullable
  • resolution_source string nullable
  • uma_resolution_status string nullable
  • group_item_title string nullable
  • start_at string nullable
  • end_at string nullable
  • created_at string nullable
  • updated_at string nullable
  • closed_at string nullable
• volume number nullable
• volume_24hr number nullable
• volume_1wk number nullable
• volume_1mo number nullable
• volume_1yr number nullable
• liquidity number nullable
• open_interest number nullable
• competitive number nullable
• comment_count integer nullable
• is_active boolean nullable
• is_closed boolean nullable
• is_archived boolean nullable
• is_new boolean nullable
• is_featured boolean nullable
• is_restricted boolean nullable
• is_neg_risk boolean nullable
• enable_order_book boolean nullable
• comments_enabled boolean nullable
• resolution_source string nullable
• start_at string nullable
• end_at string nullable
• created_at string nullable
• updated_at string nullable
• closed_at string 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 — Event not found 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.