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
Build a Polymarket Market-Making Bot in Python (2025)
End-to-end tutorial for building an automated market maker on Polymarket using the CLOB API: quoting both sides of a binary market, managing inventory, adjusting spreads on news events, and tracking P&L in USDC.
Read articlePolymarket Market-Making Bots: Quoting Both Sides of YES/NO
A technical breakdown of how market-making bots quote binary outcome shares on Polymarket's CLOB, manage inventory skew, and protect P&L through resolution.
Read articlePolymarket Conditional Token Framework: A Technical Deep Dive
Polymarket's positions are ERC-1155 conditional tokens minted via Gnosis's CTF contract on Polygon. This deep dive explains how conditions, partitions, and the CTF Exchange contract underpin every trade, resolution, and redemption on the platform.
Read article