Get which weekdays a market traded
For each weekday of a window (at most 31 days, both ends counted), whether the US market traded, read from the bars stored for it: traded, closed (a thin day with two traded weekdays after it within a week, i.e. a holiday) or unknown (a thin day without that evidence yet, so the bars may not have arrived). Built so a settlement can tell a market holiday from one instrument's missing bar; a consumer must never treat unknown as closed.
For each weekday of a window (at most 31 days, both ends counted), whether the US market traded, read from the bars stored for it: traded, closed (a thin day with two traded weekdays after it within a week, i.e. a holiday) or unknown (a thin day without that evidence yet, so the bars may not have arrived). Built so a settlement can tell a market holiday from one instrument's missing bar; a consumer must never treat unknown as closed.
Authorization
ApiKeyAuth prices:readPresent your API key as a bearer token: Authorization: Bearer pk_live_....
Two environments are issued per account. A pk_test_ sandbox key returns the SAME real historical data as a live key and does NOT consume your LIVE allowance, so learning the API is free. It has its own separate windows and can be rate limited on them. A pk_live_ key reads against your allowance.
Keys carry explicit scopes (instruments:read, prices:read, actions:read, fx:read, earnings:read, options:read, options:refresh, news:read, sentiment:read, events:read, analytics:read, correlations:read, technicals:read, macro:read) and are enforced fail-closed, so a leaked key is bounded to what it was issued for. Revocation is immediate.
In: header
Scope: prices:read
Query Parameters
Whose market. Only US is measured and offered.
Value in
- "US"
First day, inclusive (yyyy-mm-dd).
^\d{4}-\d{2}-\d{2}$Last day, inclusive (yyyy-mm-dd). The window spans at most 31 days, both ends counted.
^\d{4}-\d{2}-\d{2}$Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/market-sessions?region=US&from=string&to=string"{ "data": [ { "date": "string", "barCount": -9007199254740991, "status": "traded" } ], "meta": { "asOf": "string", "source": "string", "stale": true }}{ "error": { "code": "invalid_request", "message": "string", "docsUrl": "http://example.com", "details": { "property1": [ "string" ], "property2": [ "string" ] } }}{ "error": { "code": "invalid_request", "message": "string", "docsUrl": "http://example.com", "details": { "property1": [ "string" ], "property2": [ "string" ] } }}{ "error": { "code": "invalid_request", "message": "string", "docsUrl": "http://example.com", "details": { "property1": [ "string" ], "property2": [ "string" ] } }}{ "error": { "code": "invalid_request", "message": "string", "docsUrl": "http://example.com", "details": { "property1": [ "string" ], "property2": [ "string" ] } }}{ "error": { "code": "invalid_request", "message": "string", "docsUrl": "http://example.com", "details": { "property1": [ "string" ], "property2": [ "string" ] } }}{ "error": { "code": "invalid_request", "message": "string", "docsUrl": "http://example.com", "details": { "property1": [ "string" ], "property2": [ "string" ] } }}Get a macro time series GET
A FRED macro time series (e.g. DGS10, CPIAUCSL, VIXCLS) with its title, units, native frequency and dated observations in ascending order, optionally bounded by start and end. The series id MUST be on the published allowlist - an unknown id is rejected with invalid_request rather than proxied, so this is never an open FRED gateway. FRED encodes a missing observation as "." and those rows are OMITTED rather than coerced to 0, so a gap never reads as a real zero. When no FRED API key is configured the endpoint returns a typed unavailable error rather than a fabricated series.
Get an option contract GET
One contract by id, with its latest observed quote and its latest Greeks. Returns 404 for an unknown contract id - never an invented contract. The same Greeks honesty contract as the chain endpoint applies: provider Greeks are observations, computed Greeks carry their model and inputs, and a contract with neither is returned quote-only with the missing inputs named.