Bulk export of the data your tier already entitles, as one CSV or NDJSON file instead of per-query JSON. Grants no extra breadth: it calls the same entitled endpoint with your own key, so if you cannot GET it you cannot export it. Requires a tier with the `exports` capability (pro, enterprise); anything else receives 402.
get/v1/export
Request
- Base URL: https://kairossignal.com
- URL: https://kairossignal.com/v1/export
- Auth: none declared. Required headers: X-API-Key
Query parameters
dataset'networks' | 'grades' | 'correlations' | 'lead-lag' | 'indicators' | 'changes' | 'digest' | 'supply' | 'history' required
Which dataset to export. history accepts symbol and days.
format'csv' | 'ndjson'
csv for tabular sets (networks, grades, correlations, lead-lag, changes, indicators); ndjson for the deeply nested ones (digest, supply), where CSV flattens to thousands of columns.
Headers
X-API-Keystring required
Response
The file. X-Kairos-Export-Rows gives the row count and X-Kairos-Export-Source names the endpoint the rows came from, so any export can be re-derived from the JSON API.
Changes
No recorded changes to this operation across all 1 revision of this API.