Event and market price monitoring
Use Polymarket endpoints to turn event and market price monitoring into repeatable API requests with documented inputs and JSON responses.
Collect Polymarket event and market detail, token prices, order books, midpoints, spreads, price history, tags, sports, leaderboards, and trade activity as normalized JSON for dashboards, research, and agent-native workflows. Not investment advice or real-time trading data.
Extract Polymarket events, markets, prices, order books, tags, leaderboards, and activity as structured JSON from credential-free public Gamma and CLOB data.
Endpoint families
6
Documented params
245
Examples
65
Live catalog snapshot
Active endpoints
65
Methods
GET, POST
Required params
109
Schema refs
65
{
"platform": "Polymarket",
"endpoint": "polymarket-search",
"method": "GET",
"path": "/polymarket/search",
"auth": "apiKey"
}Related use cases
Use cases
Extract Polymarket events, markets, prices, order books, tags, leaderboards, and activity as structured JSON from credential-free public Gamma and CLOB data.
Use Polymarket endpoints to turn event and market price monitoring into repeatable API requests with documented inputs and JSON responses.
Use Polymarket endpoints to turn order book and liquidity research into repeatable API requests with documented inputs and JSON responses.
Use Polymarket endpoints to turn tag, sport, and leaderboard tracking into repeatable API requests with documented inputs and JSON responses.
Managed execution
Each Crawlora platform API is designed around a specific data surface. Instead of exposing a generic fetch endpoint, Crawlora combines endpoint-specific request logic, managed infrastructure, parsing, normalization, billing, and Playground-tested examples.
Request behavior is tuned for the target platform and endpoint type.
Supported endpoints can use managed proxy routing to improve reliability and reduce infrastructure work.
Dynamic pages can be routed through managed browser instances where JavaScript rendering is required.
Challenge pages and unusable upstream responses are detected and surfaced clearly.
Results are returned as documented JSON instead of raw HTML.
Test the same route from Docs and Playground before production integration.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/polymarket/market/{id}
/polymarket/sports
/polymarket/tag/{id}
/polymarket/teams
/polymarket/token/{token_id}/price
/polymarket/event/{slug}
Featured endpoints
/polymarket/searchSearches Polymarket's credential-free public search JSON and returns normalized event results. The `status` enum accepts `open`, `closed`, and `all`; the `sort` enum accepts `relevance`, `volume24hr`, `volume`, `liquidity`, and `endDate`.
/polymarket/eventsReturns normalized event rows from Polymarket's credential-free public Gamma events JSON.
/polymarket/event/{slug}Returns one normalized Polymarket event from credential-free public Gamma event JSON. This endpoint does not require a Polymarket user token, wallet signature, cookies, or personal account authentication.
/polymarket/marketsReturns normalized market rows from Polymarket's credential-free public Gamma markets JSON.
/polymarket/market/{id}Returns one normalized Polymarket market from credential-free public Gamma market JSON. This endpoint does not require a Polymarket user token, wallet signature, cookies, or personal account authentication.
/polymarket/token/{token_id}/priceReturns the public CLOB buy or sell price for one Polymarket token id.
Related APIs
Prediction Markets
Collect Kalshi events, markets, series, recent trades, order books, exchange schedule, and historical market candlesticks as normalized JSON for dashboards and research. Not investment advice or real-time trading data.
Prediction Markets
Collect Metaculus questions, community forecasts and forecast history, question metadata, options, and comment feeds as normalized JSON for research and tracking. Not investment, forecasting, or decision advice.
How to scrape Polymarket
Polymarket's prediction-market data is spread across several public services — events and markets, the CLOB order book, price history, and trade activity — each with its own identifiers and shapes. Crawlora's 65 Polymarket endpoints put all of it behind one key as normalized JSON. Research data, not investment advice or a trading connection.
Search events by free-text q with status and sort filters, or list events and markets ordered by 24-hour volume, total volume, liquidity, or end date.
Event detail takes a slug, with a by-id variant; market detail takes an id; the CLOB market endpoint takes a condition_id.
Per-token endpoints return price by buy or sell side, midpoint, spread, and the full order book — each with a batch variant for when you need many tokens at once.
Token price history takes an interval from 1m through max, and the activity, leaderboard, and trade endpoints cover who traded what, filtered by size band.
FAQ
Polymarket exposes several public credential-free services rather than one documented developer API, and they use different identifiers and response shapes. Crawlora's endpoints wrap them behind a single key and a consistent format so you are not integrating four services separately.
No. These endpoints are read-only market data for dashboards and research. Crawlora places no orders, is not a broker or an investment adviser, and nothing here is investment advice or a real-time trading feed.
Prices, midpoints, spreads, and order books are addressed by token_id, which comes back in the market or event detail response. Batch endpoints take several token ids in one call when you are tracking a whole market.
Token price history takes an interval of 1m, 1h, 6h, 1d, 1w, all, or max, with fidelity and explicit start and end timestamps for narrower windows.