Race weekends
API · /openf1-api
OpenF1 Live Timing API
healthy
4,533 Subscribers
Formula 1 live timing and telemetry as an API, powered by OpenF1 — clean JSON, no key. List race weekends and their sessions (practice, qualifying, sprint, race), the drivers in any session with team and colours, and dive into the timing: lap times with sector splits and speed-trap speeds, pit stops with durations, tyre stints with compound and lap range, track weather (air and track temperature, humidity, rainfall, wind), race-control messages (flags, safety cars, penalties) and team-radio clips. Granular session-by-session data from 2023 onward. Distinct from F1 reference data: this is the live-timing and telemetry layer — ideal for live dashboards, strategy and lap-time analysis, second-screen apps and Discord bots. 9 data endpoints. Authenticated with an x-oanor-key; fair-use rate limits per plan.
api.oanor.com/openf1-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 229 ms
- Server probes · 24h
- Subscribers
- 4,533
- active
- Total calls
- 190
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 3,000 calls / month
- 5 requests / second
- Hard cap (429 above quota, no overage)
- 3,000 calls/month
- 5 req/sec
- All 9 data endpoints
- Telemetry & timing
- No credit card
Starter
€7.50 /month
- 55,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 55,000 calls/month
- 15 req/sec
- Sessions, laps & stints
- Email support
Pro
€31.00 /month
- 300,000 calls / month
- 30 requests / second
- Hard cap (429 above quota, no overage)
- 300,000 calls/month
- 30 req/sec
- Live dashboards & analysis
- Priority support
Mega
€97.00 /month
- 1,300,000 calls / month
- 80 requests / second
- Hard cap (429 above quota, no overage)
- 1,300,000 calls/month
- 80 req/sec
- Broadcast & platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Formula 1 API
Formula 1 reference data as an API, built on the Ergast / Jolpica F1 dataset — every driver, constructor and circuit in F1 history plus every season since 1950. Look up a driver by id or name (e.g. hamilton → Lewis Hamilton, code HAM, #44, British), a constructor/team (ferrari → Ferrari), or a circuit with its coordinates and country (monza → Autodromo Nazionale di Monza, Italy); or search across all three (e.g. "verstappen" → Jos & Max Verstappen). 879 drivers, 214 constructors, 78 circuits. Ideal for motorsport apps, fantasy F1, sports trivia and data dashboards.
api.oanor.com/f1-api
Turbocharger Boost API
Turbocharger and boost engineering maths as an API, computed locally and deterministically — the pressure-ratio, charge-air and airflow numbers a tuner, engine builder or motorsport engineer sizes forced induction with. The pressure-ratio endpoint gives the compressor pressure ratio = absolute manifold pressure ÷ ambient = (atmospheric + boost) ÷ atmospheric, so 10 psi at sea level is a 1.68 ratio — the x-axis of every compressor map, which climbs at altitude where ambient pressure is lower. The charge-air endpoint shows why an intercooler matters: compressing air heats it (T₂ = T₁ × (1 + (PR^0.2857 − 1)/efficiency)), and hot air is less dense, so the real gain is the charge density ratio = pressure ratio × (T₁/T_charge), not the pressure ratio alone — 10 psi at 70 % compressor efficiency makes ~93 °C and a 1.37 density ratio with no intercooler, rising toward 1.6 once an intercooler claws back the heat, and the estimated power gain tracks the density. The airflow endpoint gives the engine mass airflow ≈ displacement × (rpm/2) × volumetric efficiency × charge density, in lb/min — the y-axis of the compressor map you plot against the pressure ratio to land in the efficient island and avoid surge or choke. Everything is computed locally and deterministically, so it is instant and private. Ideal for engine-tuning and turbo-sizing tools, dyno and data-logging apps, and motorsport calculators. Pure local computation — no key, no third-party service, instant. Sizing estimates — verify on a dyno. 3 compute endpoints. For engine displacement and compression use an engine API; for shop compressed air a compressor API.
api.oanor.com/turbo-api
Air-Fuel Ratio API
Air-fuel ratio and lambda maths for engine tuning as an API, computed locally and deterministically — the lambda, AFR and mixture numbers a tuner, ECU developer or motorsport engineer dials fuelling in with. The lambda endpoint turns a measured air-fuel ratio into lambda (the AFR divided by the fuel's stoichiometric AFR — 14.7 for gasoline) and the equivalence ratio φ = 1/lambda, classifying the mix as rich, stoichiometric or lean: a gasoline AFR of 13.0 is lambda 0.88, an 11.6 % rich mixture, the sort used at wide-open throttle for power and a cooler, safer burn. The afr endpoint runs it the other way — pick a target lambda and it gives the AFR the wideband should read — and because the AFR number is fuel-specific (E85's stoichiometric AFR is about 9.8, not 14.7) it always works from the right fuel, which is why pros tune in lambda when switching fuels. The mixture endpoint links the air the engine breathes to the fuel the injectors must add: give an air mass and a target lambda and it returns the fuel mass (or vice-versa), the heart of how an ECU sizes fuelling from measured airflow. Built-in stoichiometric ratios for gasoline, E10, E85, ethanol, methanol, diesel, LPG, propane, methane/CNG and hydrogen, or pass your own. Everything is computed locally and deterministically, so it is instant and private. Ideal for engine-tuning and dyno tools, ECU and standalone-management apps, motorsport and data-logging utilities. Pure local computation — no key, no third-party service, instant. 3 compute endpoints. For engine displacement and power use an engine API; for chemical reaction stoichiometry a stoichiometry API.
api.oanor.com/airfuel-api
Quarter Mile Drag API
Quarter-mile drag-strip maths as an API, computed locally and deterministically — the classic empirical estimates a racer, tuner or car enthusiast uses to relate a car's power and weight to its performance. The et endpoint gives the predicted elapsed time and trap speed from flywheel horsepower and race weight using the standard formulas — ET = 5.825 × (weight ÷ hp) raised to the one-third, trap speed = 234 × (hp ÷ weight) raised to the one-third — so a 3,000 lb car with 300 hp is predicted to run about 12.6 seconds at 109 mph, assuming a competent launch and decent traction. The horsepower endpoint runs it in reverse: because trap speed is set by power-to-weight and barely by the launch, hp ≈ weight × (trap ÷ 234) cubed is a popular way to estimate flywheel power straight off a timeslip. The power-to-weight endpoint gives the ratio that actually decides acceleration — in horsepower per pound, horsepower per ton and watts per kilogram, the cleanest cross-unit figure — with a performance class from commuter through hot hatch and supercar to hypercar, because a light 200 hp car can beat a heavy 400 hp one. Everything is computed locally and deterministically, so it is instant and private. Ideal for drag-racing and tuner apps, car-spec and comparison tools, automotive enthusiasts and motorsport dashboards. Pure local computation — no key, no third-party service, instant. Empirical estimates assuming a good launch and traction — not a timeslip. 3 compute endpoints. For aerodynamic drag use a drag API; for gearing use a gear-ratio API.
api.oanor.com/quartermile-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for OpenF1 Live Timing API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call OpenF1 Live Timing API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for OpenF1 Live Timing API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does OpenF1 Live Timing API cost?
OpenF1 Live Timing API has a free tier with 100 calls / month. Paid plans start at €7.50 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is OpenF1 Live Timing API GDPR-compliant?
All requests to OpenF1 Live Timing API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/openf1-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/openf1-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/openf1-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);import requests
r = requests.get(
"https://api.oanor.com/openf1-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
📌 Pinned
🔒 Locked
·
·
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.