Price History
Historical OHLC price data from TimescaleDB. Gaps in flat markets are forward-filled at the query layer.
/v2/prices/historyQuery Parameters
Platform identifier (required).
Platform-native market ID (required).
Start timestamp (ISO 8601). Default: 7 days ago.
End timestamp (ISO 8601). Default: now.
Candle size: 1m | 5m | 15m | 1h | 1d. Default: 1h.
Response Schema
Platform-native market ID.
Platform identifier.
Candle interval used.
OHLC candle data ordered by timestamp ascending.
Candle start time (ISO 8601).
Opening price of the interval.
Highest price during the interval.
Lowest price during the interval.
Closing price of the interval.
Last YES bid price in the interval.
Last YES ask price in the interval.
Midpoint of yes_bid and yes_ask.
Total volume during the interval.
Total dollar volume during the interval.
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 →