What the Public APIs Actually Give You (and What They Don't)

What the public APIs give you

Polymarket exposes three main public API surfaces. All are REST, no API key, no auth. Other prediction market platforms may offer similar concepts; we focus on Polymarket because it's widely used and well documented.

Gamma API — events, markets, discovery

Events are top-level questions (e.g. "Who will win the 2024 Presidential Election?"). Markets are the tradable binary outcomes (Yes/No per question, or multiple outcomes in multi-market events). You get: list/search events and markets, tags, series, sports and teams metadata. Markets include outcome labels and implied probabilities (outcome prices). So: you get full discovery—what exists, how it's categorized, and current prices for browsing or building UIs.

CLOB API — prices and order book

The CLOB (Central Limit Order Book) API gives live trading data: single-token or multi-token prices, order book (bids/asks), midpoint and spread, and prices-history (historical price data for a token). So you get everything needed to show order books, build charts, or compute mid prices and spreads.

Data API — positions, trades, analytics

The Data API is where per-user and per-market analytics live: positions and closed-positions by wallet, activity and value, and market-level trades, open interest, and holders. There is no dedicated "leaderboard" endpoint—tools (including HolyPoly) aggregate this data to compute PnL, win rates, and rankings. So: you get the raw inputs; leaderboards are derived.

What the public APIs don't give you

• Resolution / outcome determination. Deciding which outcome won is done by the Oracle (on Polymarket, UMA), not by the data APIs. The API tells you what's trading; the Oracle decides the final result. See how Polymarket's oracle and resolution work.
• Guaranteed uptime or rate limits. These are best-effort public endpoints. There is no formal SLA or documented rate limits in the same way as a paid enterprise API.
• Private order flow or internal data. You get public order book, public trades, and public positions. You don't get unfilled orders or private user data beyond what's exposed per wallet.
• A single "historical leaderboard" API. You get positions, closed positions, and trades. Building historical PnL or win rate over time requires aggregating and computing from those endpoints.

Polymarket API vs Oracle: what's the difference?

People often search "Polymarket API vs Oracle" because both terms appear in the same ecosystem. They refer to different things:

• Polymarket API = Gamma, CLOB, and Data API. They give you market data: what markets exist, current prices, order books, positions, and trades. Used for discovery, trading UIs, analytics, and copy-trading tools.
• Polymarket Oracle = the system that resolves markets. Polymarket uses the UMA Optimistic Oracle: someone proposes an outcome, others can dispute, and eventually the winning outcome is settled onchain. That result is what makes "YES" or "NO" tokens redeemable for $1 or $0.

So: API = data for trading and analysis. Oracle = who decides the final outcome. They work together but are not the same. For resolution details, see Polymarket oracle and resolution.

Polymarket historical data: what's available

"Polymarket historical data" usually means one of: (1) price over time for a market, (2) past trades, (3) past positions and PnL per wallet.

• Price history: CLOB API has prices-history for a token. You can build charts and backtests from this. Granularity and retention are per Polymarket's current API; check the API reference.
• Trade history: Data API has trades (market-level) and user activity / closed-positions. So you can reconstruct what a wallet traded and when.
• Leaderboards / PnL over time: There is no one-shot "historical leaderboard" endpoint. Tools compute win rate and PnL from positions and closed positions (and sometimes trades). HolyPoly, for example, uses the Data API and refreshes leaderboard and wallet data every 5–60 minutes—all from public endpoints.

Copy trading Polymarket: do you need the API?

You don't need to call the Polymarket API yourself to copy trade. Copy-trading tools use the public APIs to build leaderboards (who's up by win rate and PnL), wallet profiles, and playbooks (copy-ready instructions: market, side, size, entry, exit). You use the tool to see what to copy; you then execute the trades yourself on Polymarket. That keeps you in control and avoids handing over API keys or automated execution. So: the API powers the data behind the tools; you just use the UI. For a step-by-step, see how to copy trade on Polymarket and how to use HolyPoly.

Frequently asked questions

What is the difference between Polymarket API and Oracle?

The API gives you market data (events, markets, prices, order book, positions, trades). The Oracle (UMA on Polymarket) resolves which outcome won so tokens can be settled. API = data for trading; Oracle = final result.

Does Polymarket have historical data?

Yes: CLOB has prices-history; Data API has trades and closed-positions. Leaderboards and historical PnL are built by aggregating this data—there is no single historical-leaderboard endpoint.

Do I need the Polymarket API to copy trade?

No. Tools like HolyPoly use the API to show leaderboards and playbooks; you execute on Polymarket yourself. No API keys or coding required to copy trade.

Do Polymarket APIs require an API key?

No. Gamma, CLOB, and Data APIs are public REST endpoints—no key or auth. They are best-effort; there is no formal SLA.