Before you rely on it
What the Polymarket field names do not tell you, condition and token ids, what the tape holds, the error bodies and the leaderboard's offset.
condition_id is the market, token_id is one outcome
condition_id (0x hex) names a market; token_id (a long decimal string) names one outcome of it, and a binary
market has two. Market stats, Outcome candles,
Order-book snapshot and the Event tape take a
token id. Data model has the detail.
What the tape holds
The Event tape needs both window bounds and returns at most 24 hours per call, for at most 100 tokens. Its rows carry book and trade fields and no wallet address; for one trader, use the Trader profile. For whole days, download the Parquet archive instead of paging.
Errors look different here
A 400 or 503 from /v1/polymarket carries {"error": "<message>"}, a plain string, where the other namespaces answer
{"detail": ...}. REST conventions lists this namespace's other differences.
The leaderboard pages by offset
Trader leaderboard takes offset from 0 to 1000 and returns at most 50 rows per
page. The board is rebuilt hourly, so a page fetched after a rebuild can repeat or skip a wallet. Above 1000 is a 400:
narrow with category or a min_* filter.