Create export

Queue a private NDJSON export. Requires bulk.download and the selected dataset capability. parameters uses the selected security endpoint query contract. An export holds at most 1,000,000 rows and 256 MiB; a larger one ends with status failed, so split the range. Endpoint exports read the data as of when the export is built unless parameters set as_of. Alternatively use resource (collection path template) and parameters for research collections. Path IDs belong in parameters. Research exports pin as_of at creation. Neither kind takes limit or cursor in parameters: an export reads every page of the result.

POST/v1/exports
Required capability
bulk.download
Data timing
As published by the source
Credits
500 credits per request.
Live endpoint. Request examples query live data with your API key; response examples are illustrative. History and coverage vary by dataset and plan; see dataset coverage.

Parameters

No query parameters. Authentication is still required.

JSON request body

JSON
{
  "endpoint": "eod",
  "parameters": {
    "symbols": [
      "XNAS:AAPL"
    ],
    "from": "2026-09-01",
    "to": "2026-09-25"
  }
}

Response fields

Returns data as an object. All example values are illustrative.

idstring
id
statusstring
status

Response metadata

Responses include meta.timezone. Dataset responses include next_cursor; health and exports have their own metadata. Request tracing uses the X-Request-ID header.

Read the shared data conventions

When something goes wrong

An empty data: [] is a successful query with no matching records. Invalid symbols, permissions and malformed parameters produce an RFC 9457 problem with an actionable detail.

Error codes & retry guidance

Plans

Requires bulk.download. Access, recency and history depth come from the plan definitions the API enforces.

PlanAccessRecencyHistory
FreeNot included——
DeveloperNot included——
ProNot included——
CommercialIncludedSame as the exported datasetNot date-bounded
ScaleIncludedSame as the exported datasetNot date-bounded

Exports also require the capability of the dataset being exported.

History is how far back a plan may request. How far records actually go for a symbol is history_from in dataset coverage. Nothing is real-time. Compare plans