> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Record an export order

> An optional template for keeping a record of a Bulk Exports order, filled from the order page and the metadata inside each downloaded file.

This page is optional. Keep a record when you may need to show later exactly what you bought: for an audit, a research log, or a support request. Every value comes from the order page in [your exports](https://0xarchive.io/dashboard/exports) or from the metadata inside each downloaded file, so nothing has to be noted down during checkout.

## Where each value comes from

| Field | On the order page | In each file's metadata |
| - | - | - |
| Order ID | Under the **Export Order** title | `export_job_id` |
| Venue and symbol | Each line of **Order Details** | `exchange`, `symbol` |
| Data type | Each line of **Order Details** | `data_type` |
| UTC dates | Each line of **Order Details** | `date_range` |
| Size and price | Each line of **Order Details**, then **Subtotal**, **Credits applied**, **Discount applied**, and **Total** | |
| Files | **Download Files**: file names and sizes | |
| Timestamps | **Created**, **Paid**, and **Completed**, in UTC, below the order details | `exported_at` |

[Check what you bought](/exports/quickstart#5-check-what-you-bought) shows how to read file metadata in Python. If you plan to publish, share, or build a product on the data, record that decision too; [Data rights](/data-rights) explains when written permission is needed.

## Check the files against the record

Before you rely on a set of files, confirm they match the order. Each file's `exchange`, `symbol`, `data_type`, and `date_range` metadata should match one line of **Order Details**, and its `export_job_id` should equal the order ID. Every row's timestamp should fall on a UTC date inside that line's range. If a file does not match, [contact support](https://0xarchive.io/contact) with the order ID. Keep the `README.md` from the download with the files: it lists each file with its size and documents every column.

## Template

Copy this into your records, one entry per order, with one item for each line of **Order Details**. The values shown are an example:

```json theme={"theme":"github-dark"}
{
  "order_id": "copy from under the Export Order title",
  "created_utc": "2026-10-01 00:00",
  "completed_utc": "2026-10-01 00:01",
  "total_usd": "10.00",
  "credits_applied_usd": "0.00",
  "items": [
    {
      "venue": "hyperliquid",
      "symbol": "BTC",
      "data_type": "trades",
      "start_date_utc": "2026-10-01",
      "end_date_utc": "2026-10-01",
      "size_gb": "0.19",
      "price_usd": "7.50",
      "files": ["BTC_trades_2026-10-01_to_2026-10-01.parquet"]
    }
  ],
  "data_rights_decision": "internal research only"
}
```

## Next step

<Card title="Read the files you bought" icon="table" href="/schemas/export-files">
  See the columns, types, row order, and timestamps of every export file.
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.