DOCS/GETTING STARTED
API v1 (draft)

Finance Data Cloud documentation

One schema for trades, quotes, funding and full-depth order books across every venue we capture. These pages are the reference for API v1: the data model first, then the four ways to get data out.

Status. The v1 specification is a draft. Endpoints go live with Phase 1 (Hyperliquid), with early access for pre-registered partners targeted for Q1 2027 and general availability in Q2 2027. Field names and endpoints documented here are the ones we are building to; changes before launch are recorded in the changelog.

Five-minute path

01Install the SDKpip install fdc on Python 3.9 or later.
02Use a test keyKeys starting fdc_test_ return a fixed 24-hour sample, so you can build against real rows before your plan starts.
03Pull trades, rebuild a book, open a streamEach step takes a few lines of Python, with the equivalent curl call next to it.

Concepts

How the data is shaped and why. Read these before writing anything that depends on ordering, book state or completeness.

Access

The same rows, delivered four ways. Pick by workload: the SDK for research notebooks, REST for services, WebSocket for live trading systems, S3 for bulk backfills.

Extended data

Base URLs

InterfaceEndpoint
RESThttps://api.financedatacloud.com/v1
WebSocketwss://stream.financedatacloud.com/v1
Bulk S3s3://fdc-archive/{dataset}/venue={venue}/date={YYYY-MM-DD}/{symbol}.parquet
Pythonpip install fdc

REST, WebSocket and the SDK authenticate with the same API key, sent as Authorization: Bearer fdc_live_.... S3 access is granted to your AWS account instead. Details on Authentication.

Getting help

Questions about the API or the data go to daniel@financedatacloud.com; include the X-Request-Id header from the response if you have one. Security reports go to daniel@financedatacloud.com, and our practices are described on Security. Planned venues and dates are on the roadmap, and service health on Status.