REST API / Polymarket (Admin) / Volume Chart

Volume Chart (Polymarket, by Condition)

ADMIN-ONLY (gated, not yet public). Per-period volume for a Polymarket market with YES/NO breakdown, aggregated from market_trades. YES/NO labels resolved via clob.polymarket.com/markets/<condition_id>; non-Yes/No markets fall back to the first/second outcome labels (e.g. Up/Down crypto). Bucket presets: hour (90d max), day (1y max), week (3y max). Data begins at 2026-04-28T22:28:14Z; earlier values are not represented in the response.

GET/v2/polymarket/volume-chart/{condition_id}

Query Parameters

condition_idstring (path)Required

Polymarket condition ID (path parameter).

bucketstring

Bucket size: hour | day | week. Default: hour.

start_tsinteger

Start of range, unix seconds. Default: 2026-04-28T22:28:14Z.

end_tsinteger

End of range, unix seconds. Default: now.

Response Schema

condition_idstring

The Polymarket condition ID.

bucketstring

Bucket size: hour | day | week.

bucket_secondsinteger

Bucket size in seconds.

yes_token_idstring | null

Resolved YES outcome token ID.

no_token_idstring | null

Resolved NO outcome token ID.

yes_outcome_labelstring | null

Outcome label used for the YES side (e.g. "Yes", "Up").

no_outcome_labelstring | null

Outcome label used for the NO side (e.g. "No", "Down").

seriesobject[]

Per-bucket volume with YES/NO breakdown, ascending by t.

tinteger

Bucket start (unix seconds).

total_dollarnumber

Total dollar volume in this bucket.

total_sharenumber

Total share volume in this bucket.

yes_dollarnumber

Dollar volume on the YES side.

no_dollarnumber

Dollar volume on the NO side.

yes_sharenumber

Share volume on the YES side.

no_sharenumber

Share volume on the NO side.

_metaobject

Data warning metadata.

data_available_fromstring

ISO8601 timestamp before which trade data is missing.

warningstring

Plain-text caveat about the data window.

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.

Request HeaderX-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:

Response Headers (global)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: 412

If 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

Demo Mode

Verified

Parameters

Condition IDRequired

Bucket

Start (unix seconds)

End (unix seconds)

Response

—

Click EXECUTE to send a request →