formula-api

Formula 1 data, live and archived, from one API.

REST for everything we store, and live WebSockets for the session in progress. Timing, telemetry, race control, weather and circuits, kept as the source sent it.

  • REST + WebSocket
  • Live timing
  • Car telemetry
  • Weather forecasts
  • Source data untouched

What's covered

Formula 1 today, with every dataset served in the shape we store it.

Live timing

A WebSocket streams positions, laps, intervals, pit stops, stints, weather and race control as a session runs. Joining mid-session gives you the current state first, then the live feed.

Session data over REST

Meetings, sessions, drivers, laps, intervals, positions, stints, pit stops, overtakes, results, starting grids and both championships. Every column is a filter.

Car telemetry and location

Per-car telemetry and track location for finished sessions, archived in 30-second chunks and served as plain JSON. Live sockets can limit telemetry to the cars you pick.

Race control, translated

Race control messages with car numbers resolved to drivers, alongside the original message untouched.

Weather

Measured weather per session, plus forecasts around each session at the circuit, with a five-day outlook and a playback of past race weekends.

Circuits

Track layouts with corners and marshal sectors and circuit coordinates, ready to draw or place on a map.

How it works

Built to be trustworthy first, then fast.

  1. We keep our own copy

    Data from each provider is stored in its own tables, unaltered, so the archive is ours and your requests never depend on a provider being up.

  2. Live goes straight to storage

    During a session the feed is written as it arrives, then served to REST and to connected clients.

  3. Checked and corrected

    Each weekend is re-read before every session and every night, so revisions and penalties are picked up.

  4. Closed by design

    Every request carries an API key. Nothing under the API is public.

One request away

Every endpoint lives under /v1/{series}/ and takes the key in a header. Every column is a filter, with limit and offset for paging.

curl "https://data.formula-api.com/v1/formula-1/next-race" \
  -H "X-API-Key: YOUR_KEY"

Access

formula-api is a private, key-gated API. Keys are issued by us and sent in the X-API-Key header on every request.

Frequently asked questions

Short answers to the usual ones.

Is the API public?

No. Every request to the API needs an API key, and keys are issued by us. The API is closed to the public.

Which series are covered?

Formula 1 today. Each series is its own namespace under /v1, so more series can be added alongside it without changing what exists.

Is there live data?

Yes. A live WebSocket carries timing and race control during a session, with separate sockets for car telemetry and car location. REST serves the same data once it is stored.

How far back does the data go?

The API focuses on recent seasons and builds forward; it is not a full historical archive. Car telemetry and location archives currently cover 2025 and 2026.

Is the data modified?

Provider data is stored as the provider sent it, with nothing trimmed or reshaped. Anything we derive lives in separate tables of our own.

Does the data get corrected after a session?

Yes. The calendar and each weekend are re-checked against the source before every session and again every night, so a stewards decision or a source correction reaches the API.