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
Every figure below is read from the live Polymarket endpoint catalog — 65 endpoints, 245 documented request parameters, and 65 published response schemas — the same catalog Docs and Playground run against.
65 documented Polymarket endpoints, grouped into 25 request families — Market, Sports and Tag, plus 22 more.
245 request parameters are documented across those Polymarket endpoints, 109 of them required — the full input contract is public before you write any integration code.
65 of the 65 Polymarket endpoints ship a recorded example response, and 65 carry a documented response schema — you can code against the real JSON before the first request.
Polymarket endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
30 hosted MCP tools back the Polymarket endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/polymarket/market/{id}
/polymarket/sports
/polymarket/tag/{id}
/polymarket/teams
/polymarket/token/{token_id}/price
/polymarket/event/{slug}
Featured endpoints
/polymarket/searchSearches Polymarket and returns event results. The `status` enum accepts `open`, `closed`, and `all`; the `sort` enum accepts `relevance`, `volume24hr`, `volume`, `liquidity`, and `endDate`.
Response notes
- Empty valid searches return an empty `events` array. - `events[].markets` contains the nested markets returned by Polymarket for each event. - Invalid `status` or `sort` values return an invalid-parameter error before upstream IO.
MCP tool polymarket_search
/polymarket/eventsLists Polymarket events with their markets. Sort by 24-hour volume, total volume, liquidity, end date and more, filter to open or closed events, and page with `limit` (default 25, max 100) and `offset`. Each event has its slug, description, end date, liquidity, open interest and comment count; each market has its question, outcomes, best bid and ask, last trade price and volume.
Response notes
- Invalid enum or identifier values return invalid-parameter errors before upstream IO. - This endpoint is not investment advice or real-time trading data.
MCP tool polymarket_events
/polymarket/event/{slug}Returns one Polymarket event. This endpoint does not require a Polymarket user token, wallet signature, cookies, or personal account authentication.
Response notes
- Returns one event. - This is a public read-only endpoint and does not require a Polymarket user token, wallet signature, cookies, or personal account authentication. - Nested markets use the same `MarketSummary` shape as Polymarket list endpoints.
MCP tool polymarket_event_detail
/polymarket/marketsLists Polymarket markets, up to `limit` rows (default 25, max 100), starting at `offset` (default 0, max 10000). Sort with `order`, such as `volume24hr` or `liquidity`, flip direction with `ascending`, and filter with `closed`. Each market has its question, slug, prices, volume, liquidity, token ids and outcomes.
Response notes
- Invalid enum or identifier values return invalid-parameter errors before upstream IO. - This endpoint is not investment advice or real-time trading data.
MCP tool polymarket_markets
/polymarket/market/{id}Returns one Polymarket market. This endpoint does not require a Polymarket user token, wallet signature, cookies, or personal account authentication.
Response notes
- Returns one market. - This is a public read-only endpoint and does not require a Polymarket user token, wallet signature, cookies, or personal account authentication. - Outcome prices, liquidity, volume, best bid, best ask, and last trade price are returned as numeric fields when values are available.
MCP tool polymarket_market_detail
/polymarket/token/{token_id}/priceReturns the current price for one Polymarket outcome token, identified by the required `token_id`. `side` is `buy` or `sell` and defaults to `buy`. The response gives the `price` as a number, the `side` used and a `fetched_at` time. It is a snapshot, not trading advice.
Response notes
- Returns the public CLOB buy or sell price for one token id. - This is a read-only public CLOB snapshot and is not investment advice or trading instruction.
MCP tool polymarket_token_price
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.