> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/polymarket/us-series>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/polymarket/us-series.mdx>

---

# Polymarket US Series API

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

`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`.

## Request

- **Endpoint:** `GET /v1/polymarket/us/series`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by page
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/polymarket/us/series/get)
- **Platform page:** [/platforms/polymarket](https://www.socialfetch.dev/platforms/polymarket)

## 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.