Social Fetch
Start for freeStart free
Polymarket hub

Polymarket US Events API

Events on the Polymarket US exchange, with every market attached.

GET /v1/polymarket/us/events

1 credit Failed requests are free

Try in playgroundFull API docs

About this endpoint

GET /v1/polymarket/us/events returns data.events from the Polymarket US exchange. Each event has id, slug, title, description, category, status, active, closed, archived, live, period, image, seriesSlug, dates, tags, marketCount and markets[] with the US market shape. status filters open (default) or closed.

limit is 1 to 100 and defaults to 20. An event carries all of its markets, so a page of 100 can weigh several megabytes. Pages are cut by position, so an event added or closed while you walk can repeat or skip a row: walk quickly, or de-duplicate by id.

Polymarket US Events API FAQ

Is Polymarket US the same as the main Polymarket event market?

No. It is a separate exchange with its own route group, ids, market states and fields. Use /v1/polymarket/us for it and /v1/polymarket/events for the main event market.

Why can paging repeat or skip an event?

Pages are cut by position, not by a stable cursor. If an event is added or closed while you walk, the positions shift. Walk quickly, or de-duplicate the events you collect by id.

How large can a page be?

A page of 100 events can weigh several megabytes because each event carries every market. Ask for fewer if you only need titles and headline numbers.

What does lookupStatus mean on this route?

found means the object or list was returned. not_found means no matching object exists. HTTP 200 only means the request finished, so branch on data.lookupStatus before storing a row.

How much does this route cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.

Other Polymarket endpoints