Batch Prices
GET /v1/markets/{id} individually.
Request
Batch Size Limits
The maximum number of markets per request depends on your API key’s rate limit tier:
Exceeding your tier’s limit returns a
400 BATCH_LIMIT_EXCEEDED error.
The authoritative per-tier value is on the wire via GET /v1/keys/tiers
(the max_batch_size field). The schema-level hard ceiling is 50, but
since the highest tier (enterprise) caps at 25, you will hit your
tier limit long before the ceiling.
POST /v1/prices/batch vs POST /v1/prices
PolySimulator provides two batch price lookup endpoints tailored for condition IDs vs token IDs:
For convenience, POST /v1/prices/batch also accepts the token-based shapes as aliases, avoiding footgun errors when porting between SDKs.
Response
Markets with unavailable prices return only the
condition_id field —
all price fields will be absent. This can happen when a market is newly
listed and hasn’t been cached yet. Always check for the presence of
buy/sell before using them.Use Cases
- Portfolio valuation: Fetch current prices for all your positions at once
- Watchlist monitoring: Track prices for markets you’re interested in
- Batch strategies: Evaluate multiple markets before submitting batch orders
Error Handling
Next Steps
- Markets — Full market metadata
- Order Book — Detailed liquidity depth