Polymarket

11 endpoints under https://data.vike.io/v1/polymarket/. Nine are over the Polymarket CLOB as recorded by Vike — not a proxy of Polymarket's own API; two are trader routes over the on-chain trade tape. They answer on the same host, behind the same API key and the same hourly budget as every other namespace.

Every endpoint here is GET: any other method returns 405 {"detail":"Method Not Allowed"}, and a path that is not a route returns 404 {"detail":"Not Found"} — FastAPI's own bodies, which are not the {"error": ...} shape a rejected parameter gets.

Start here

What it looks like in use

# find: bitcoin markets by slug; each row carries a condition_id and two token_ids
curl -s "https://data.vike.io/v1/polymarket/markets?query=bitcoin&limit=3" \
  -H "X-API-Key: $VIKE_API_KEY"

# orient: TOKEN is one token_id from a row above; first_ms and last_ms bound its recorded tape
curl -s "https://data.vike.io/v1/polymarket/market_stats?token_id=$TOKEN" \
  -H "X-API-Key: $VIKE_API_KEY"

# chart: FIRST_MS is that first_ms; bars come oldest first, so this is the first 48 hourly probability candles
curl -s "https://data.vike.io/v1/polymarket/ohlcv?token_id=$TOKEN&interval=1h&from=$FIRST_MS&limit=48" \
  -H "X-API-Key: $VIKE_API_KEY"

# drill in: FROM and TO are epoch milliseconds one hour apart inside that span; the trade prints in it, 100 to a page
curl -s "https://data.vike.io/v1/polymarket/events?token_id=$TOKEN&event_type=trade&from_ms=$FROM&to_ms=$TO&limit=100" \
  -H "X-API-Key: $VIKE_API_KEY"

# page: has_more was true, so repeat the call with the response's next_cursor
curl -s "https://data.vike.io/v1/polymarket/events?token_id=$TOKEN&event_type=trade&from_ms=$FROM&to_ms=$TO&limit=100&cursor=$CURSOR" \
  -H "X-API-Key: $VIKE_API_KEY"

An unrecognised query parameter is refused rather than ignored, as 400 {"error":"unknown query parameter 'x' (this endpoint accepts: …)"}. On the market-data routes (everything except /wallets/{address} and /smart_money) a value that does not parse as a number or a boolean falls back to that parameter's default instead of failing. The two trader routes validate instead: a bad window, mode, hours, limit or address is a 400. On every route an empty value counts as absent and a repeated parameter takes its last value.

One spelling

/v1/polymarket/... is the only form. Seven older flat paths — /v1/markets, /v1/markets/{condition_id}, /v1/market_stats, /v1/ohlcv, /v1/orderbook, /v1/settlements/{condition_id} and /v1/events — answered until 2026-09-03 and now return 404. They predated the namespace and were retired once the usage record showed that, across its whole history, they had served 28 requests, all from the owner's own key.

Identifiers: condition_id and token_id

A market has a condition_id and each of its outcomes has a token_id, and the two are not interchangeable; Polymarket data model says which endpoint takes which.

One call gets you both, and it is the right first call in this namespace:

curl -H "X-API-Key: $VIKE_API_KEY" \
  "https://data.vike.io/v1/polymarket/markets?query=bitcoin&limit=3"

Each row carries the market's condition_id and its two token_ids; every market-data endpoint here takes one or the other. /markets shows the response.

The endpoints

Bulk archive discovery

Two endpoints that index the Parquet archive rather than serving market data. They tell you what partitions exist and where to download them; the files themselves are served from https://data.vike.io/archive/, and the archive pages cover the layouts, the schemas and — importantly — how to download without exhausting your budget.

Both are namespaced-spelling only. There is no /v1/archive/... flat alias.

Metering

Every call in this namespace spends one unit of the same hourly budget as MCP and the other /v1 namespaces — see Rate limits. Archive downloads from https://data.vike.io/archive/ do not spend it, but the two discovery endpoints above are ordinary API calls and do.

The mistake this namespace invites is worth repeating from that page: if you want book history rather than a snapshot, download whole archive partitions and read them locally. Pointing a Parquet client at an archive URL issues a request per column chunk, and one file can produce tens of thousands of them.

REST and MCP: which routes share code

Both surfaces are served from the same code where it matters, and they are not one-to-one:

The second Polymarket MCP server that once answered at data.vike.io/mcp (nine tools, one per route) was retired on 2026-09-03 with zero authenticated calls in its history. There is one MCP server, and the Polymarket tools are on it; data.vike.io/mcp now reaches that same server.

Related

• Bulk archive — full L2 book events, the taker tape and derived top-of-book as Parquet, and the download guidance the two discovery endpoints above lead to.
• Rate limits · Authentication