Download center

Overview

You can access and manage all data downloads on the Download center page of your Databento portal. After you submit a download request, we prepare the flat files on the backend and then save them to the Download center.

Finding previous downloads

You can search for downloads in the Download center search bar. You can search by the following:

• Request timestamp. Search for a specific date range.
• Dataset. Search by dataset.
• Schema. Search by schema.
• Encoding. Search by encoding (DBN, CSV, JSON).

You can filter your search results with the following:

• Request timestamp. Filter by a specific date range.
• Dataset. Filter by dataset.
• Schema. Filter by schema.
• Encoding. Filter by encoding (DBN, CSV, JSON).
• Status. Downloads have statuses of either Queued, Processing, Ready, or Expired.

You can also sort by request time and billed size.

Interpreting download statuses

Downloads have the following statuses:

• Queued. We process download requests one by one. When a request has been Queued, it's been placed at the end of the "line" and will be processed.
• Processing. The request is at the front of the "line." We are actively preparing the files on the backend.
• Ready. The request is now a file that's ready for your use.
• Expired. The file has expired and can no longer be downloaded. You need to submit a new download request to access the data. Files expire 30 days after a download request has been submitted.

Download details

See also

Data can be downloaded from the API with batch.download.

Clicking on a download will open up the details of the request. This page will show various details about the download request, which includes the symbols, time range, and customizations selected.

Each file can be downloaded one at a time by clicking on the download icon next to each file. Additionally, all files can be downloaded at once in a zip file by clicking on "Download all".

Support files

Each completed batch job package includes the following three supporting JSON files:

• condition.json

• manifest.json

• metadata.json

• condition.json: This file outlines the dataset condition per date and aids in identifying the appropriate data for processing, including any missing or pending days. The same information can be obtained from metadata.get_dataset_condition endpoint.

• manifest.json: This file lists all the batched data and support files contained in the package, including file names, sizes, and SHA-256 hashes. You can use this information to confirm that your data is complete and free of tampering or corruption. The same information can be obtained from batch.list_files endpoint.

• metadata.json: This file describes the original request for the batch download, including any advanced customization options. The same information can be obtained from the batch.list_jobs endpoint.

If the requested data does not contain symbology information, one or more symbology support files will be included. Each data file will come with an associated symbology file. This file will be named similarly to the data file, except it will end with *.symbology.json. This file is only provided when symbol mapping was not requested when using the CSV or JSON encodings. Additionally, for CSV encodings an alternative CSV representation of this file is provided for convenience. These symbology support files provides symbology mappings for the batched data. This allows you to interpret the integer instrument IDs and map these to their corresponding raw symbols across date intervals. The same information can be obtained from the symbology.resolve endpoint.

FTP

Databento also supports downloading data with FTP. FTP is ideal for downloading large datasets reliably, with the ability to browse directories and download multiple files at once. It's well suited for downloading recurring batch requests. Various FTP clients such as FileZilla and lftp can be used to download data.