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+by+team' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"team":"Required"}'
{"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"}'
[{"constructor":"Williams","wins":114,"percentage":13.32}]
curl --location --request POST 'https://zylalabs.com/api/6510/f1+database+api/9630/get+statistics+by+team' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"team":"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."
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
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.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
9,435ms
Service Level:
100%
Response Time:
63ms
Service Level:
100%
Response Time:
694ms
Service Level:
100%
Response Time:
5,335ms
Service Level:
100%
Response Time:
743ms
Service Level:
100%
Response Time:
63ms
Service Level:
100%
Response Time:
8,117ms
Service Level:
100%
Response Time:
66ms
Service Level:
100%
Response Time:
53ms
Service Level:
100%
Response Time:
2,795ms
Service Level:
100%
Response Time:
238ms
Service Level:
100%
Response Time:
1,278ms
Service Level:
100%
Response Time:
1,394ms
Service Level:
100%
Response Time:
335ms
Service Level:
100%
Response Time:
1,062ms
Service Level:
100%
Response Time:
260ms
Service Level:
100%
Response Time:
319ms
Service Level:
100%
Response Time:
818ms
Service Level:
100%
Response Time:
12,889ms
Service Level:
100%
Response Time:
2,477ms