Polymarket hub

Polymarket US Series API

Series on the Polymarket US exchange, with ids, slugs and timestamps.

GET /v1/polymarket/us/series

1 credit Failed requests are free

About this endpoint

GET /v1/polymarket/us/series returns a page of series in data.series. Each row has id, slug, title, createdAt and updatedAt. The US exchange groups its events into series such as a league season, and this route lists them.

limit is 1 to 100 and defaults to 50. data.page continues with an opaque cursor. This is the US exchange series list; the main event market has its own series routes under /v1/polymarket/series.

Polymarket US Series API FAQ

How do I get the events in a series?

Use the US events list and match on seriesSlug from an event, or fetch a US event by id or slug. This route lists the series themselves, not their events.

Is this the same as /v1/polymarket/series?

No. The US exchange has its own series with its own ids and fields. The main series routes include recurrence, volume and related events; this route carries id, slug, title and timestamps.

How do I page the list?

Pass data.page.nextCursor as cursor while data.page.hasMore is true. The cursor is opaque and tied to this operation, so do not build one yourself.

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.