Polaris Data API Reference

Polaris provides REST endpoints at https://api.polaris.supply. Most endpoints are public. Add bearer auth only when you need broader historical access, account-tier visibility, or a dataset policy that requires it. Choose the endpoint that matches your task, then read the smaller page for that endpoint.

Use the SDKs first. Most users should connect to and fetch data from Polaris through the Python, TypeScript, or Rust SDK. Calling the REST API directly is only for debugging, building SDKs, or building middleware involving Polaris.

Start with the right endpoint

Task	Page
Understand when you need an API key and how bearer auth works	Quickstart
Discover valid sources, markets, and time bounds	Catalog
List available snapshot files (standard or raw)	Snapshots
Get bulk download URLs for a UTC date, or download a snapshot file by key	Download

Endpoint families

Metadata

GET /catalog for public market discovery, with optional account-tier visibility when you send bearer auth

Historical files

GET /snapshots for public hourly snapshot listing. Add raw=true to list venue-native raw snapshot files (requires paid auth)
GET /download for bulk daily download manifests or single-file download. Use source/market/date for the bulk JSON manifest, or key for one file

Common response patterns

/snapshots returns a paginated JSON response:

{
  "source": "hyperliquid",
  "market": "BTC",
  "access": { "status": "open", "public_cutoff_date": null },
  "total": 2,
  "total_bytes": 987654321,
  "limit": 2,
  "has_more": false,
  "next_cursor": null,
  "snapshots": []
}

/download supports two response shapes: a bulk daily manifest when you request source, market, date, and mode=json, or a single-file redirect / JSON URL response when you request key.

Next steps

Read Quickstart to get the SDK running before you make direct requests.
Read Market coverage if you are deciding between snapshots and direct API queries.
Read Trades if you want the simplest recent-data method.

​Start with the right endpoint

​Endpoint families

​Metadata

​Historical files

​Common response patterns

​Recommended reading order

​Next steps

Start with the right endpoint

Endpoint families

Metadata

Historical files

Common response patterns

Recommended reading order

Next steps