The F1 Database API specializes in delivering detailed information related to the Formula 1 racing domain. It processes various types of data fields, including race schedules, results, driver and team statistics, and historical performance metrics. Key data structures include arrays for race results, objects for driver profiles, and nested data for team compositions. The API utilizes domain-specific terminology such as 'constructors', 'drivers', 'qualifying', and 'race weekend', adhering to standards like JSON for data interchange. Technical requirements include authentication for accessing certain endpoints and rate limiting to ensure fair usage. The output format is structured in JSON, with a schema that includes fields for race dates, driver names, team affiliations, lap times, and points scored. This API is essential for developers and analysts looking to integrate or analyze Formula 1 data within applications or for research purposes.
{"season":"2025","races":[{"round":1,"race_name":"FORMULA 1 LOUIS VUITTON AUSTRALIAN GRAND PRIX 2025","date":"14-16 Mar","location":"Australia"},{"round":2,"race_name":"FORMULA 1 HEINEKEN CHINESE GRAND PRIX 2025","date":"21-23 Mar","location":"China"},{"round":3,"race_name":"FORMULA 1 LENOVO JAPANESE GRAND PRIX 2025","date":"04-06 Apr","location":"Japan"},{"round":4,"race_name":"FORMULA 1 GULF AIR BAHRAIN GRAND PRIX 2025","date":"11-13 Apr","location":"Bahrain"},{"round":5,"race_name":"FORMULA 1 STC SAUDI ARABIAN GRAND PRIX 2025","date":"18-20 Apr","location":"Saudi Arabia"},{"round":6,"race_name":"FORMULA 1 CRYPTO.COM MIAMI GRAND PRIX 2025","date":"02-04 May","location":"Miami"},{"round":7,"race_name":"FORMULA 1 AWS GRAN PREMIO DEL MADE IN ITALY E DELL'EMILIA-ROMAGNA 2025","date":"16-18 May","location":"Emilia-Romagna"},{"round":8,"race_name":"FORMULA 1 TAG HEUER GRAND PRIX DE MONACO 2025","date":"23-25 May","location":"Monaco"},{"round":9,"race_name":"FORMULA 1 ARAMCO GRAN PREMIO DE ESPA\u00d1A 2025","date":"30-01 May-Jun","location":"Spain"},{"round":10,"race_name":"FORMULA 1 PIRELLI GRAND PRIX DU CANADA 2025","date":"13-15 Jun","location":"Canada"},{"round":11,"race_name":"FORMULA 1 MSC CRUISES AUSTRIAN GRAND PRIX 2025","date":"27-29 Jun","location":"Austria"},{"round":12,"race_name":"FORMULA 1 QATAR AIRWAYS BRITISH GRAND PRIX 2025","date":"04-06 Jul","location":"Great Britain"},{"round":13,"race_name":"FORMULA 1 MO\u00cbT & CHANDON BELGIAN GRAND PRIX 2025","date":"25-27 Jul","location":"Belgium"},{"round":14,"race_name":"FORMULA 1 LENOVO HUNGARIAN GRAND PRIX 2025","date":"01-03 Aug","location":"Hungary"},{"round":15,"race_name":"FORMULA 1 HEINEKEN DUTCH GRAND PRIX 2025","date":"29-31 Aug","location":"Netherlands"},{"round":16,"race_name":"FORMULA 1 PIRELLI GRAN PREMIO D\u2019ITALIA 2025","date":"05-07 Sep","location":"Italy"},{"round":17,"race_name":"FORMULA 1 QATAR AIRWAYS AZERBAIJAN GRAND PRIX 2025","date":"19-21 Sep","location":"Azerbaijan"},{"round":18,"race_name":"FORMULA 1 SINGAPORE AIRLINES SINGAPORE GRAND PRIX 2025","date":"03-05 Oct","location":"Singapore"},{"round":19,"race_name":"FORMULA 1 MSC CRUISES UNITED STATES GRAND PRIX 2025","date":"17-19 Oct","location":"United States"},{"round":20,"race_name":"FORMULA 1 GRAN PREMIO DE LA CIUDAD DE M\u00c9XICO 2025","date":"24-26 Oct","location":"Mexico"},{"round":21,"race_name":"FORMULA 1 MSC CRUISES GRANDE PR\u00caMIO DE S\u00c3O PAULO 2025","date":"07-09 Nov","location":"Brazil"},{"round":22,"race_name":"FORMULA 1 HEINEKEN LAS VEGAS GRAND PRIX 2025","date":"20-22 Nov","location":"Las Vegas"},{"round":23,"race_name":"FORMULA 1 QATAR AIRWAYS QATAR GRAND PRIX 2025","date":"28-30 Nov","location":"Qatar"},{"round":24,"race_name":"FORMULA 1 ETIHAD AIRWAYS ABU DHABI GRAND PRIX 2025","date":"05-07 Dec","location":"Abu Dhabi"}]}
curl --location --request POST 'https://zylalabs.com/api/6510/f1+database+api/9421/get+f1+races' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{"season":"2025","standings":[{"position":1,"team_name":"McLaren","points":188},{"position":2,"team_name":"Mercedes","points":111},{"position":3,"team_name":"Red Bull Racing","points":89},{"position":4,"team_name":"Ferrari","points":78},{"position":5,"team_name":"Williams","points":25},{"position":6,"team_name":"Haas","points":20},{"position":7,"team_name":"Aston Martin","points":10},{"position":8,"team_name":"Racing Bulls","points":8},{"position":9,"team_name":"Alpine","points":6},{"position":10,"team_name":"Kick Sauber","points":6}]}
curl --location --request POST 'https://zylalabs.com/api/6510/f1+database+api/9422/obtain+f1+teams' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{"drivers":[{"name":"Oscar Piastri","team":"McLaren","points":99},{"name":"Lando Norris","team":"McLaren","points":89},{"name":"Max Verstappen","team":"Red Bull Racing","points":87},{"name":"George Russell","team":"Mercedes","points":73},{"name":"Charles Leclerc","team":"Ferrari","points":47},{"name":"Kimi Antonelli","team":"Mercedes","points":38},{"name":"Lewis Hamilton","team":"Ferrari","points":31},{"name":"Alexander Albon","team":"Williams","points":20},{"name":"Esteban Ocon","team":"Haas","points":14},{"name":"Lance Stroll","team":"Aston Martin","points":10},{"name":"Pierre Gasly","team":"Alpine","points":6},{"name":"Nico Hulkenberg","team":"Kick Sauber","points":6},{"name":"Oliver Bearman","team":"Haas","points":6},{"name":"Isack Hadjar","team":"Racing Bulls","points":5},{"name":"Carlos Sainz","team":"Williams","points":5},{"name":"Yuki Tsunoda","team":"Red Bull Racing","points":5},{"name":"Fernando Alonso","team":"Aston Martin","points":0},{"name":"Liam Lawson","team":"Racing Bulls","points":0},{"name":"Jack Doohan","team":"Alpine","points":0},{"name":"Gabriel Bortoleto","team":"Kick Sauber","points":0}]}
curl --location --request POST 'https://zylalabs.com/api/6510/f1+database+api/9423/get+f1+drivers' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{"Driver":"Max Verstappen","Wins":{"Total":1,"From pole":1,"Win & f.lap":"-","Hat-trick":"-"},"Podiums":{"Total":3,"1st":1,"2nd":2,"3rd":"-"},"Pole positions":{"Total":2,"Pole & win":1},"Fastest laps":{"Total":0,"Win & f.lap":"-"},"Points finishes":{"Total":5,"Points":87,"Points per points finish":17.4},"Front row starts":{"FR starts":2,"Pole":2,"2nd":"-"},"Retirements":{"DNFs":1}}
curl --location --request POST 'https://zylalabs.com/api/6510/f1+database+api/9424/get+f1+drivers+stats' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"driver":"Required"}'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The F1 Database API provides comprehensive data on Formula 1 racing, including race results, driver statistics, team information, and event schedules.
The API uses JSON format for data interchange, with key data structures including arrays for race results, objects for driver profiles, and nested data for team compositions.
Yes, certain endpoints of the F1 Database API require authentication to access, ensuring secure usage of the data.
The F1 Database API implements rate limiting to ensure fair usage, which restricts the number of requests a user can make within a specific time frame.
Each endpoint returns specific data related to Formula 1 racing. For example, the "get F1 races" endpoint provides race schedules, while "obtain F1 teams" returns constructor standings. The "get F1 drivers" endpoint lists drivers and their points, and "get F1 drivers stats" offers detailed statistics for individual drivers.
Key fields include "season," "race_name," "date," and "location" for races; "position," "team_name," and "points" for teams; and "name," "team," and "points" for drivers. The driver stats endpoint includes fields like "Wins," "Podiums," and "Retirements."
The response data is structured in JSON format. For example, race data is organized in an array of race objects, each containing details like round number and race name. Driver stats are presented in a nested format, detailing various performance metrics.
The "get F1 drivers stats" endpoint requires a driver name as a parameter to retrieve specific statistics. Other endpoints do not require additional parameters, as they return data for the entire season or all drivers/teams.
Users can customize requests by specifying driver names in the "get F1 drivers stats" endpoint. This allows for targeted retrieval of statistics for individual drivers, enhancing the relevance of the data returned.
Typical use cases include developing applications for F1 fans, conducting statistical analysis for research, and creating visualizations of race results and driver performance. Analysts can leverage the data for insights into team and driver trends.
Data accuracy is maintained through regular updates and validation against official Formula 1 sources. The API ensures that the information reflects the latest race results, driver standings, and statistics.
Users can expect consistent data patterns, such as arrays for multiple entries (e.g., races or drivers) and nested objects for detailed statistics. For instance, driver stats will typically include multiple performance metrics organized under specific categories like "Wins" and "Podiums."
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the βX-Zyla-API-Calls-Monthly-Remainingβ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
10,192ms
Service Level:
100%
Response Time:
723ms
Service Level:
100%
Response Time:
700ms
Service Level:
100%
Response Time:
3,963ms
Service Level:
100%
Response Time:
6,631ms
Service Level:
100%
Response Time:
2,795ms
Service Level:
100%
Response Time:
809ms
Service Level:
100%
Response Time:
12,191ms
Service Level:
99%
Response Time:
1,790ms
Service Level:
93%
Response Time:
1,032ms