Polymarket API. Prediction markets as JSON.

Yes. Social Fetch has 42 Polymarket routes under /v1/polymarket: events, event lookup, insights, annotations, comments, markets, market lookup by id, slug or condition id, batch market lookup, order books, prices, price history, trades, holders, tags, series, sports, teams, search, movers, user profiles, positions, activity, stats, PnL, leaderboards, biggest wins, Perps and Polymarket US. Authenticate with your Social Fetch API key in x-api-key.

Call GET /v1/polymarket/events/{eventIdOrSlug}. On data.lookupStatus: found, each market in data.event.markets has a conditionId and an outcomes array. Each outcome has a tokenId. Pass up to 150 token ids to GET /v1/polymarket/books (query tokenIds, comma separated or repeated) or to GET /v1/polymarket/prices. The market endpoint returns the full record, including fees and resolution rules.

found means the object or list was returned. not_found means no event, market, tag, series, token or wallet matched. HTTP 200 only means the request finished, so branch on data.lookupStatus before writing. Some lists describe an empty result as found with an empty array, such as a market with no trades yet.

Every list response has data.page with hasMore and nextCursor. Pass data.page.nextCursor as the cursor query parameter and keep the other filters unchanged. The cursor is an opaque string tied to one operation; it is not a timestamp or an offset you can build yourself. When hasMore is false, stop.

GET /v1/polymarket/books and GET /v1/polymarket/prices charge one credit per token id, with a maximum of 150 ids per request. GET /v1/polymarket/markets/batch charges one credit per condition id or token id, with a maximum of 100 ids. The batch response summary reports requested, found and notFound. Confirm the charge with meta.creditsCharged.

Use interval=1h, 6h, 1d, 1w, 1m, max or all for a preset range, or pass from and to as unix seconds with bucketSeconds between 60 and 86400. A custom from and to window spans at most 15 days. Points come oldest first, and each point carries at, price and bucketSeconds. Walk a longer history in several 15-day windows.

Use GET /v1/polymarket/users/{wallet}/positions for open, closed, redeemable or mergeable positions, GET /v1/polymarket/users/{wallet}/activity for the action history, GET /v1/polymarket/users/{wallet}/stats for headline figures and a PnL breakdown, and GET /v1/polymarket/users/{wallet}/pnl for a series over time. The leaderboard and biggest wins routes rank wallets across the market. A wallet that never traded returns an empty list or not_found, not an error.

No. Perpetual futures live under /v1/polymarket/perps (instruments, tickers, klines, book, trades, leaderboard), and the US exchange lives under /v1/polymarket/us (events, event, market, series). They have their own ids, fields and rules, so the route groups keep them separate. Polymarket US is a different exchange from the main Polymarket event market.

Comments are keyed by numeric event id and return an empty list when an event has none; an id that does not exist returns not_found. Insights are machine-written context and can be null for an event that has none. Annotations explain dated price moves and only exist for events with large moves, so an empty array is normal. All three are read-only and never trade.

No. Every Polymarket route on Social Fetch is read-only. There is no signing, order placement, cancellation, deposit or wallet connection. The routes return public market data, public trade and holder rows, and public wallet profiles and positions.