TradingView UDF config
Endpoint
Section titled “Endpoint”GET /api/dtao/tradingview/udf/configDescription
Section titled “Description”Returns the TradingView Universal Data Feed (UDF) configuration for the dTao chart datafeed. The response advertises supported resolutions (1, 5, 15, 60, 1D, etc.), the list of exchanges, currency codes, and the boolean feature flags that TradingView’s Charting Library expects from a /config endpoint (supports_search, supports_marks, supports_timescale_marks, supports_group_request).
This endpoint is part of the TradingView UDF protocol and is called automatically by a TradingView UDFCompatibleDatafeed instance pointing at /api/dtao/tradingview/udf. Companion endpoints in the same feed:
/api/dtao/tradingview/udf/symbol_info— per-symbol metadata./api/dtao/tradingview/udf/history— OHLCV bars for a symbol + resolution.
Parameters
Section titled “Parameters”No parameters.
Responses
Section titled “Responses”200 — Config retrieved successfully
Section titled “200 — Config retrieved successfully”Media: application/json
Schema
{ "type": "object", "required": [ "supported_resolutions", "supports_group_request", "supports_marks", "supports_search", "supports_timescale_marks", "currency_codes", "exchanges" ], "properties": { "currency_codes": { "type": "array", "items": { "type": "object", "required": [ "id", "code", "description" ], "properties": { "code": { "type": "string" }, "description": { "type": "string" }, "id": { "type": "string" } } } }, "exchanges": { "type": "array", "items": { "type": "string" } }, "supported_resolutions": { "type": "array", "items": { "type": "string" } }, "supports_group_request": { "type": "boolean" }, "supports_marks": { "type": "boolean" }, "supports_search": { "type": "boolean" }, "supports_timescale_marks": { "type": "boolean" } }}Try it
Section titled “Try it”Interactive request console coming soon. In the meantime you can use the OpenAPI spec with any client (Insomnia, Bruno, Scalar, curl).
Authentication
Section titled “Authentication”All Taostats API requests require an Authorization header containing your API key. See Getting Started.