Manage your subscription, find your API credentials, and fix the most common issues, all in one place.
Billing is handled by Stripe. Payment method, invoices and cancellation are all in the billing portal.
Your username and password were emailed to you right after you signed up. To find that email:
OpenF1.Still nothing? Contact us with the email address you paid with and we will re-send some new credentials.
Authenticated access works in three steps:
https://api.openf1.org/token.
Authorization: Bearer <token> header.
Before contacting us or opening an issue, please run this command,
replacing YOUR_USERNAME and YOUR_PASSWORD.
It tells us (and you) whether the problem is your credentials or your
code.
curl -X POST "https://api.openf1.org/token" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "username=YOUR_USERNAME&password=YOUR_PASSWORD"
access_token
Your credentials are fine and the problem is on the client side. The
usual culprits: sending JSON instead of
application/x-www-form-urlencoded, using
GET instead of POST, reusing a token older
than an hour, or forgetting the Bearer prefix in the
Authorization header.
YOUR_PASSWORD.
As an authenticated user, you get:
That is double the free-tier REST limits. If you hit them, cache responses and back off before retrying rather than looping on errors. For live data, prefer MQTT or WebSocket over polling.
No, credits are not required in your project. They are always appreciated though, and a link back to openf1.org helps other people find the API. :)
Technical questions and bug reports are best asked in public, so others with the same problem can find the answer. Anything about billing or credentials should come to us directly.