VenueMarketOutcome.id. GET /charts/bars supplies canonical API history and mutable tails; GET /charts/history/manifest supplies authorized references to immutable finalized objects served directly by CDN. See Market-data API for delivery states, signed-URL handling, read quotas, and native module Worker integration.
That endpoint returns one canonical bar series for a single outcome and resolution using
TradingView-style [from, to) and countBack semantics. Aggregate charts are not supported.
- SDK (vanilla JS/TS)
- Hooks (React)
- UI Components
Supported resolutions
GET /charts/bars supports four resolutions. The SDK takes the human-readable
form and translates it; if you are calling the REST endpoint directly you must
send the wire value, and the parameter is named resolution — there is no
interval parameter.
from and to are epoch milliseconds; to is required. An unrecognised
query parameter is ignored rather than rejected, so a request that sends
interval=1h silently falls back to the default 5-minute resolution.
Bars are not stored. Every request is served live from the venue’s own
historical-price API, so the depth of history available depends on the venue.
When a venue returns no bars for the requested window,
data is empty and
meta.lastBarOpenTime / meta.staleSeconds are null — overlay the live WS
midpoint to draw a line for a market that has not traded yet.How it works
Related
WebSocket Protocol
Subscribe, authenticate, handle heartbeats, and reconnect safely.
Real-Time Orderbook
Reuse the same orderbook stream for depth views and chart inputs.
User Notifications
Handle authenticated order and balance events on the same socket.