What is Polymarket Gamma API?

An event groups one or more questions, while an individual binary market represents a YES/NO contract with its own rules and dates. Keep IDs, slugs and token mappings distinct rather than treating an event URL as one executable market.

The checked /markets/keyset response contains markets and next_cursor. A sampled CTF market included id, conditionId and JSON-encoded outcomes and clobTokenIds; labels and tokens must retain index alignment. This sample does not establish identical fields or an available CLOB book for every protocol version.

Who it is for

Building searchable market catalogs.
Research pipelines needing definitions and tags.
Sports apps linking games, teams and contract types.

Features and coverage

Events
Read a known event or paginate through a feed.
Markets
Retrieve binary contracts and downstream identifiers.
Tags and filters
Narrow by category, status and supported attributes.
Series
Group recurring events by theme.
Sports metadata
Discover leagues, teams, moneyline, spread and totals markets.
Game-linked discovery
Use game IDs to find companion markets instead of guessing slug suffixes.
Keyset response
Read markets and next_cursor and parse encoded outcome/token arrays where present.

Workflows with Polymarket Gamma API

Build a catalog

Paginate open events, preserve IDs and slugs and map outcomes to tokens. Refresh market status separately from live prices.

Link sports data

Resolve game and team order, then discover props and additional lines with the game ID.

Resolve a pasted link

Look up its event or market by URL or slug, then pass the relevant identifiers to book queries.

Map a CTF book

Keep Gamma id distinct from conditionId. Parse outcomes and tokens in matching order and pass the chosen token to CLOB; stop if token data or an enabled book is absent.

Pricing and total cost

Public discovery needs no authentication. The guide lists no separate subscription for these reads.

Getting started

Before you start: Pagination is needed for a complete catalog.

Choose the event, market or series level.
Request a small filtered page.
Preserve IDs, slugs, tags and outcome-token mappings.
Use CLOB for executable prices and books after discovery.

An event can contain several markets rather than one YES/NO contract.

Read Polymarket API documentation

Useful links

Join Polymarket Discord

What to check

Pagination is needed for a complete catalog.
Rules and dates belong to each individual contract.
Sports home/away ordering can change after rescheduling.
Sampled CTF fields do not establish token or book availability for every protocol version.

A closer look

Ratings & reviews

Editorial rating

4.0/ 5

0 user reviews

PredictionToolkit editorial

Our take on Polymarket Gamma API

Public discovery and structured metadata make Gamma a useful catalog starting point. Complete coverage still needs pagination and careful separation of events and contracts.

Based on documented features, setup and access terms. How we rate

User reviews 0

The main score switches to user ratings after 5 published reviews.

Be the first to share your experience

A specific example helps the next person choose the right tool.

Related tools

Browse category

Frequently asked questions about Polymarket Gamma API

How do events and markets differ?

An event groups questions; a binary market represents one YES/NO question.

Does Gamma place orders?

No. Order placement belongs to CLOB.

How do I find related sports markets?

Use the game ID and current listing workflow.

Is every list response a bare array?

No. The checked /markets/keyset response is an object with markets and next_cursor. Match the parser to the selected route.

Polymarket Gamma API: Event and Market Discovery API

Screenshots and interface