Datafeed configuration
https://atlas-api.skylit.ai/v1/configThe static UDF DatafeedConfiguration — supported resolutions,
exchanges, symbol types, and feature flags. Free.
Also carries max_fetch_trading_days: the /v1/history
request-window cap, keyed by every advertised resolution. Read it once
at startup and size your history pages from it, rather than hardcoding a
window that later drifts — or discovering the limit by being rejected,
which costs a credit each time. This call is free precisely so the limit
is knowable in advance.
The values are served from the same limits the server enforces, so they cannot disagree with it. A charting client can ignore the field: it is not part of the UDF spec, and TradingView skips config keys it does not recognise.
⚠ Cached for an hour (max-age=3600), so treat a 400 naming a
max_days SMALLER than your cached value as authoritative and re-read
this endpoint.
Authorization
Authorization: Bearer <your API key>Required. A missing header returns 401; an invalid, revoked or expired key returns 403.
Responses
- 200
Datafeed configuration.
- 401
Missing or invalid API key.
Response fields
supports_searchbooleansupports_group_requestbooleansupports_marksbooleansupports_timescale_marksbooleansupports_timebooleansupported_resolutionsstring[]max_fetch_trading_daysobjectMax trading days one
/v1/historyrequest may span, keyed by resolution. Resolutions sharing a bar tier share a value —60,240and480all read hourly bars and all cap at 720.intraday_multipliersstring[]exchangesobject[]valuestringnamestringdescstring
symbols_typesobject[]namestringvaluestring
Last updated