← Developer tools

Find your toolkit

Polymarket APIs and data providers | Page 2

Choose an API by the information your application needs and how it must arrive. Official endpoints and third-party providers can serve different roles in market discovery, prices, order books, wallet research and historical analysis.

How to choose data apis

Start with the entity you need

Gamma is the starting point for market metadata, CLOB for an outcome-token book, and Data API for public wallet activity or rankings. A provider’s broad market coverage does not mean every route returns the same records or identifiers.

Compare the exact route

  • Keep event IDs, Gamma market IDs, condition IDs and outcome-token IDs distinct when joining responses.
  • Read the response envelope and pagination scheme: Gamma keyset responses use markets or events; Data v2 paged reads use data and pagination.
  • Check dataset coverage, history, stream support, rate limits and output format for the endpoint you will actually call.
  • Compare authentication and provider access terms separately from the choice of client library.

Public data reads and authenticated account actions need different handling. A route for reading a book is not permission to submit a signed order. Establish that boundary before selecting an SDK, stream or assistant connection.

88 tools · 13–24 shown

Narrow your search

Find the right tools

Official Polymarket CLOB price and book documentation
Data API4.0Editorial

Read outcome prices and depth, then handle authenticated orders through a separate signing boundary.

  • Access API
Official Polymarket public analytics integration guide
Data API4.0Editorial

Retrieve positions, trades, holders and rankings while preserving outcome IDs and pagination context.

  • Access API
Official Polymarket Gamma API market-discovery documentation
Data API4.0Editorial

Discover contracts and their identifiers before querying executable prices or building a searchable catalog.

  • Access API
Polymarket public sports channel and heartbeat documentation
Data API4.0Editorial

Bring live scores, periods and game status into a sports-market interface.

  • Access API
Probalytics historical warehouse with an SQL result example
Dataset4.0Editorial

Historical market and trade data, with full-depth books on higher tiers and SQL, SDK and bulk-export access.

  • Access API
The Odds API introduction with response example and plan entry points
Data API4.0Editorial

An external bookmaker-data feed for sports-price comparisons, with scores, historical snapshots and spreadsheet add-ons.

  • Access API
TickFoundry dataset entry page with an illustrative book ladder
Dataset4.0Editorial

UTC market-day downloads and browser book-and-trade replay for studying how recorded execution costs change with order size.

  • Access Web · API
0xinsider sports wallet patterns and linked-position examples
Analytics3.5Editorial

Compare sports prices and graded-wallet exposure, inspect unusual trades and connect the same research to an API.

  • Access Web · API · MCP
Adanos Polymarket stock-sentiment API and ticker-discovery entry
Data API3.5Editorial

Compare stock-related prediction activity with social and news sentiment using shared API access.

  • Access API · CLI
Adjacent editorial market research and newsletter archive
Research tool3.5Editorial

Follow themes across event contracts using constructed indices, reference rates, research dashboards and market briefings.

  • Access Web · API · Email
ArbBets entry page showing cross-venue YES/NO price comparison
Data API3.5Editorial

Scan matched outcomes across venues and inspect sizing, prices and costs through the web app or paid API.

  • Access Web · API
ARBITER unified API entry page and sample market view
Data API3.5Editorial

Query normalized markets, historical books, wallet analytics and possible event matches across Polymarket and Kalshi.

  • Access API