Polymarket — List events (keyset pagination)

Retrieve events using cursor-based (keyset) pagination for stable, efficient paging through large result sets with the Polymarket API. The sample response includes titles. Request fields include next-page cursor (after_cursor), result limit (limit), result offset (offset). Use it for on-chain or crypto market research. The GET request schema also lists order, ascending. Use the data in market research, dashboard views, or scheduled data collection for the relevant markets.

Selected price
$0 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Optional parameters (41)
Maximum number of results to return (max 100)
Comma-separated list of JSON field names to order by
Sort direction. Only used when order is set.
Opaque cursor token from a previous response's next_cursor
Not allowed. Returns 422 if provided.
id
slug
Filter by closed state. Omitted includes open and closed events. Use true for closed events, false for open events, or any (case-insensitive) for both states. Unlike markets, any does not require an identifier filter. Invalid closed values return 422. Import profile accepts the boolean branch only; other union branches are not exposed.
live
featured
cyom
title_search
liquidity_min
liquidity_max
volume_min
volume_max
start_date_min
start_date_max
end_date_min
end_date_max
start_time_min
start_time_max
tag_id
tag_slug
Tag IDs to exclude. Cannot overlap with tag_id.
related_tags
tag_match
series_id
game_id
event_date
event_week
featured_order
recurrence
created_by
parent_event_id
include_children
When set, external_partners are attached to matching events
When true, includes Chats and Series.Chats relations
When true, includes Templates relation
When true, includes BestLines relation
locale

Sample response

"$schema": "https://gamma-api.polymarket.com/schemas/EventsKeysetListResponse.json"
events [2]
[0] {}
"active": true
"creationDate": "2024-12-31T19:05:45.901361Z"
descriptionString · text preview
events[0].description
This market will resolve to "Yes" if Kraken (US-based cryptocurrency exchange) completes an Initial Public Offering (IPO) by December 31, 2025, 11:59 PM ET, as confirmed by official company announcements or credible news sources. The IPO refers to the first sale of stock by Kraken to the public on any recognized stock exchange.

If Kraken merges with another entity, is acquired, or ceases to exist before the market resolves, the market will also resolve to "No".

This market will resolve early if Kraken completes an IPO by December 31, 2025, 11:59 PM ET.

The resolution source for this market 
"endDate": "2028-01-01T04:59:00Z"
"icon": "https://polymarket-upload.s3.us-east-2.amazonaws.com/will-kraken-ipo-in-2024--_GT-GzKWtUW.jpg"
"id": "16183"
"image": "https://polymarket-upload.s3.us-east-2.amazonaws.com/will-kraken-ipo-in-2024--_GT-GzKWtUW.jpg"
"resolutionSource": ""
"slug": "kraken-ipo-in-2025"
"startDate": "2024-12-31T19:05:45.901363Z"
"ticker": "kraken-ipo-in-2025"
"title": "Kraken IPO by ___ ?"
[1] {}
"active": true
"creationDate": "2025-01-03T19:35:04.095064Z"
descriptionString · text preview
events[1].description
This market will resolve to "Yes" if Emmanuel Macron ceases to be President of France for any length of time between January 2 and December 31, 2025, 11:59 PM ET (inclusive). Otherwise, this market will resolve to "No".

If Macron departs from office before the expiry date, the market should resolve immediately.

The primary resolution source for this market will be information from the government of France, however a consensus of credible reporting will also be used.
"endDate": "2027-01-01T04:59:00Z"
"icon": "https://polymarket-upload.s3.us-east-2.amazonaws.com/macron-out-in-2025-qFUc7czZE3Ev.jpg"
"id": "16263"
"image": "https://polymarket-upload.s3.us-east-2.amazonaws.com/macron-out-in-2025-qFUc7czZE3Ev.jpg"
"resolutionSource": ""
"slug": "macron-out-in-2025"
"startDate": "2025-01-03T19:35:04.095066Z"
"ticker": "macron-out-in-2025"
"title": "Macron out by...?"
"next_cursor": "0d4LIEDhFKhyUMngKj_M_BNmjH7Ab0CJV7KSPSbHdqd7InYiOjEsImsiOiJldmVudHMiLCJvaCI6IjRmNTNjZGExOGMyYmFhMGMwMzU0YmI1ZjlhM2VjYmU1ZWQxMmFiNGQ4ZTExYmE4NzNjMmYxMTE2MTIwMmI5NDUiLCJrZXlzIjpbeyJ0Ijoic3RyaW5nIiwidiI6IjE2MjYzIn1dfQ"

Response result

Response structure

Inferred from examples
  • $schemastring
  • eventsobject[]
    • activeboolean
    • creationDatestring
    • descriptionstring
    • endDatestring
    • iconstring
    • idstring
    • imagestring
    • resolutionSourcestring
    • slugstring
    • startDatestring
    • tickerstring
    • titlestring
  • next_cursorstring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Polymarket — List events (keyset pagination) with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.