Volume Chart (Polymarket, by Condition)
Trading volume time series for a Polymarket market, broken down by YES and NO outcome, computed from market trades.
/v2/polymarket/volume-chart/{condition_id}Query Parameters
Polymarket condition ID (path parameter).
Bucket size: hour | day | week. Default: hour.
Start of range, unix seconds. Clamped to >= 2026-05-19T00:00:00Z (the served floor).
End of range, unix seconds. Default: now.
Response Schema
The Polymarket condition ID.
Bucket size: hour | day | week.
Bucket size in seconds.
Resolved YES outcome token ID.
Resolved NO outcome token ID.
Outcome label used for the YES side (e.g. "Yes", "Up").
Outcome label used for the NO side (e.g. "No", "Down").
Per-bucket volume with YES/NO breakdown, ascending by t.
Bucket start (unix seconds).
Total dollar volume in this bucket.
Total share volume in this bucket.
Dollar volume on the YES side.
Dollar volume on the NO side.
Share volume on the YES side.
Share volume on the NO side.
Data warning metadata.
ISO8601 served floor — earlier ranges are not served (2026-05-19T00:00:00Z).
Plain-text coverage statement.
Error Responses
All errors return the same envelope. The code field is stable and programmatically branchable; error and message are human-readable. errors[] is present only on validation failures with field-level detail. See the full error code reference →
Always `false` on error responses.
Short, human-readable title (e.g. 'Invalid API Key.').
Human-readable explanation for the error. Safe to surface in UIs.
Stable, hierarchical machine-readable code (e.g. 'validation.invalid_enum'). Use for programmatic handling.
Link to this code's entry in the Error Reference.
Optional. Present only on validation failures with field-level detail.
Name of the offending parameter.
Field-level machine code.
Human-readable explanation.
Authentication
API Key
To secure your requests, we strongly recommend passing your API key via the X-API-Key header. This prevents sensitive keys from being exposed in access logs or browser history.
X-API-Key: pmx_test_5e8f...Rate Limits
API rate limits are enforced based on the tier associated with your API key. Limits are tracked on two dimensions: requests per second and requests per month. Each completed request counts toward the global monthly quota. Separate endpoint-group monthly limits (matched markets, arbitrage, EV) only advance when the response body has success: true.
Usage is returned on responses via headers such as:
X-RateLimit-Limit-Second: 10X-RateLimit-Remaining-Second: 9X-RateLimit-Limit-Month: 1000X-RateLimit-Remaining-Month: 842Example (endpoint-group, when applicable)X-RateLimit-Limit-Arb-Month: 500X-RateLimit-Remaining-Arb-Month: 412If you exceed a rate limit, the API returns a 429 status with a Retry-After header indicating when you can resume.
Request
Live API Key
Parameters
Response
—Click EXECUTE to send a request →