Export historical data

Outcome

Create one Data Catalog export selection and leave a traceable order record for the resulting file or checkout state.

Prerequisites

Start with the export page supplied by the Data Catalog. Copy its current browser URL instead of constructing a path from a symbol.
Choose one market, one schema or small schema set, and one explicit UTC range.
Read Export schemas for the selected schema key and Data rights before downstream distribution.
Have the account or payment method needed to complete checkout. The browser flow is separate from the public REST contract.

Inputs

Field	Bounded value
Catalog URL	`https://0xarchive.io/data`
Market	The venue, symbol or outcome, and export page URL selected in the Data Catalog
Schema	One key such as `trades`, `l2_orderbook`, or `oi`
Range	`30D`, `90D`, `1Y`, `All`, or `Custom` UTC dates
Selection state	`selected`, `schemas`, `range`, and, for `Custom`, `start` and `end`
Completion condition	Dashboard job reaches a named state and the file metadata is saved

Steps

Choose the market

Open /data, choose the venue and market, and retain the current export page URL. Do not infer the URL from a symbol.

Choose the schema and range

Select the smallest useful schema set and one range. The browser presets are 30D, 90D, 1Y, and All; use Custom when the job needs explicit UTC start and end dates.

Review the quote

Record the selected market, schema keys, coverage window, estimated size, rows, credits, pricing unit, and minimum before confirming the order.

Confirm and monitor

Use the authenticated browser checkout flow, then keep the order ID and open its export detail page at /dashboard/exports/:id. Do not build a client around browser checkout calls that are not published REST routes.

Check the delivered file

Confirm the file format, schema key, row timestamps, market identity, and downstream loader behavior before widening the selection.

Expected state

The export is one of these observable states: pending, paid, processing, completed, or failed. A completed order exposes a downloadable file from its dashboard detail page. A failed or pending order still has enough selection and quote metadata for recovery or support.

Verification

Treat the browser selection as product state, not a REST request. Confirm the exchange:symbol:data_type cart identity, where data_type is the selected schema key. For HIP-4 selections, preserve the field set (hip4_event, hip4_contracts, hip4_side) when the UI supplies it. Compare the selected schema coverage key and window with Export schemas before ordering.

Failure and recovery

The selected market has no requested schema or window: stop and choose a schema-specific range shown by the catalog.
The estimate changes: save the new quote context and review it before confirming.
Login interrupts checkout: keep the selected market, schemas, range, and quote context, then return through the dashboard.
failed: keep the job ID, selected items, quote context, and error message. Do not assume a second order has the same estimate.
Rights do not cover the intended downstream use: stop before download or distribution and follow Data rights.

Saved run metadata

{
  "source_url": "https://0xarchive.io/data",
  "export_page_url": "copy the current browser URL from the Data Catalog",
  "venue": "record Hyperliquid or Lighter",
  "market_type": "record perpetuals, spot, HIP-3, or HIP-4",
  "market": "record the symbol, pair, or outcome identity",
  "schema_keys": ["trades"],
  "selection": {
    "selected": "record the UI selection state",
    "schemas": "trades",
    "range": "custom",
    "start": "record UTC start",
    "end": "record UTC end"
  },
  "cart_item": "exchange:symbol:data_type",
  "data_type": "the selected schema key",
  "quote": "record size, rows, price, credits, and minimum",
  "job_id": "record the dashboard export ID",
  "delivery_status": "pending | paid | processing | completed | failed",
  "data_rights_decision": "record the transformation and source-exposure decision"
}

Next task

Use Export checkout for state and recovery details, Export schemas for the schema contract, or Data rights before publishing or redistributing output.

​Outcome

​Prerequisites

​Inputs

​Steps

​Expected state

​Verification

​Failure and recovery

​Saved run metadata

​Next task