Historical

Request a historical export

Historical exports are prepared manually today. Send the raw dataset, markets, date range, preferred Parquet, CSV, or JSONL format, and delivery destination. We confirm captured coverage and scope before promising the export.

What can be exported

Raw events captured by the storage pipeline can be requested. Raw financial values retain their decimal-string representation and raw event fields stay aligned with the live streams. Availability varies by dataset and date range.

Dataset	One row per	Highlights
trades	executed fill	price, size, notional, wallet, realized PnL, fees, maker/taker, liquidation flags
orders	order-status event	captured placements, cancels, fills, triggers, and rejections
book_updates	order-book delta	captured changes to the order books
top_of_book	tick	best bid/ask per market over time
twaps	algo status	institutional TWAP executions and progress
events	ledger/market event	funding payments and rates, liquidations, deposits, withdrawals

Requesting an export

An export request names the dataset, the markets, the date range, the format, and where to put it. Send these details through the contact form. The JSON below is a requirements template, not an API request:

export-request.jsonjson

{  "dataset": "trades",  "markets": ["BTC", "ETH", "@107"],  "from": "2026-05-01",  "to": "2026-06-01",  "format": "parquet",  "destination": "s3://your-bucket/robinhoodrpc/"}

markets accepts perps (BTC), spot pairs (@107), and HIP-3 markets (dex:SYMBOL); omit it for all 462+ markets.
destination takes an s3:// or gs:// URI you have granted us write access to, or is omitted for direct download links.
Date ranges are UTC days, inclusive of from, exclusive of to, so re-running a request is idempotent per partition.

Delivered layout

Files arrive partitioned by dataset and UTC date, with a manifest listing row counts and checksums so you can verify completeness before loading:

s3://your-bucket/robinhoodrpc/  trades/    dt=2026-05-01/part-00000.parquet    dt=2026-05-01/part-00001.parquet    dt=2026-05-02/part-00000.parquet    ...  manifest.json   # datasets, ranges, row counts, checksums

Choosing a format

Format	Best for	Notes
parquet	Backtesting and analytics at scale (DuckDB, pandas, Spark)	Columnar, compressed, typed. The default choice.
csv	Spreadsheets, quick inspection, legacy loaders	Header row included; one file per partition.
jsonl	Replaying events through stream-shaped consumers	One JSON object per line, nested fields (e.g. liquidation detail) preserved as objects.

Custom datasets

If you need an aggregate or joined shape rather than raw events, request a custom dataset. Examples include OHLCV, wallet PnL, liquidation, and funding outputs. We verify the underlying captured range before agreeing the schema or delivery.

One-off delivery is scoped manually. Ask about recurring delivery if you need it; it is promised only when included in the accepted scope.
Export pricing and delivery timing are quoted for the requested data range and shape; there is no automatic plan quota.
Start a custom request via contact. Include datasets, markets, range, format, and destination.

Schemas: column-by-column reference for every dataset above.
Replay & backfill: replay recent stream data from a block within the last 6 hours.