Skip to main content
GET
Get historical ticks for a single symbol

Overview

Each tick is a pair trade on one contract: the price paid for YES, the matching price for NO, and the traded quantity. Pass the contract symbol — the same symbol returned by search and event contracts.

Time range

from and to are both optional and both inclusive. Each accepts either an RFC3339 timestamp or a Unix epoch value in seconds or milliseconds:
Omit both to take the service default window. Omitting only one leaves that side unbounded.

Limit

limit caps the number of ticks returned. 0 or an omitted value means 10,000, and any larger value is clamped to 10,000 — the response never reports a limit larger than the one actually applied. To walk a longer history, page by narrowing from/to rather than by raising limit.

Prices are strings

yesPrice and noPrice are exact decimals serialized as JSON strings:
Parse them with a decimal type. Reading them into a binary float loses precision at the tick sizes these contracts trade at.

Example

Errors

  • 400 — symbol missing, or from/to/limit failed validation
  • 502 — the upstream data store was unavailable
Both return the prediction-market error envelope: success: false with a structured error object.

Query Parameters

symbol
string
required
Example:

"HORC_1126_Republican"

from
string

RFC3339 timestamp or Unix seconds/milliseconds.

Example:

"2026-04-01T00:00:00Z"

to
string

RFC3339 timestamp or Unix seconds/milliseconds.

Example:

"2026-04-20T00:00:00Z"

limit
integer

0 or omitted means 10000; values above 10000 are clamped to it.

Required range: 0 <= x <= 10000
Example:

500

Response

Historical ticks

Standard success envelope used by all success responses. data is endpoint-specific.

success
boolean
required
Example:

true

data
object