Polymarket Gamma vs Data vs CLOB API: Which One Does Your Bot Need?
Polymarket API architecture: market discovery, account data and live order-book execution.
Polymarket API architecture: market discovery, account data and live order-book execution.
Gamma API
Use Gamma for market metadata, events, tags and discovery. Cache descriptive data, but do not treat it as the low-latency execution feed.
Data API
Use the public Data API for positions, trades, activity and holder analytics. It is valuable for research, wallet tracking and reconciliation.
CLOB API
Use CLOB endpoints for books, prices, history and authenticated order management. A trading bot must maintain book sequence and separate public data from signed actions.
Architecture
Join APIs through stable condition and token identifiers, timestamp responses and degrade safely when one surface is unavailable.
See Polymarket bot development and our market scanner.
Building this for production?
We turn this architecture into tested, non-custodial software with monitoring, documentation and deployment support.
Related technical guides
Polymarket API Authentication in Python: Wallet and CLOB Setup
Configure Polymarket CLOB authentication in Python: signer types, API credentials, EIP-712 signatures and a safe first order using py-clob-client.
Read articlePolymarket Arbitrage: Where the Edge Actually Is
Prediction markets misprice constantly. Here's where the real arbitrage lives on Polymarket — complementary outcomes, cross-market relationships and resolution mechanics.
Read articleSplitting & Merging Polymarket CTF Positions Programmatically
A working guide to Polymarket conditional tokens split merge calls on the Gnosis CTF, and how bots trade the 1.00-sum invariant across binary outcomes.
Read article