{"years":[1950,1951,1952,1953,1954,1955,1956,1957,1958,1959,1960,1961,1962,1963,1964,1965,1966,1967,1968,1969,1970,1971,1972,1973,1974,1975,1976,1977,1978,1979,1980,1981,1982,1983,1984,1985,1986,1987,1988,1989,1990,1991,1992,1993,1994,1995,1996,1997,1998,1999,2000,2001,2002,2003,2004,2005,2006,2007,2008,2009,2010,2011,2012,2013,2014,2015,2016,2017,2018,2019,2020,2021,2022,2023,2024]}
curl --location --request POST 'https://zylalabs.com/api/7054/f1+title+holders+api/10944/get+all+championship+years' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{"year":2022,"driver_name":"Max Verstappen"}
curl --location --request POST 'https://zylalabs.com/api/7054/f1+title+holders+api/10945/get+champion+by+year' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"year":"Required"}'
{"Driver":"Max Verstappen","Titles":1,"Season":2022,"Age":25,"Chassis":"Red Bull","Engine":"RBPT","Tyres":"P","Poles":7,"Wins":15,"Podiums":17,"Fastest laps":5,"Points":454,"% Points":76.174,"Clinched":"Round 18 of 22","# of rounds remaining":4,"Margin":146,"% Margin":32.159}
curl --location --request POST 'https://zylalabs.com/api/7054/f1+title+holders+api/10946/get+champion+data+by+name+and+year' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"driver":"Required","year":"Required"}'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the F1 Title Holders API simply include your bearer token in the Authorization header.
| 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.
(Save 2 months with annual billing 🎉)
The API provides structured data on Formula One World Drivers' Champions. The "get all championship years" endpoint returns a list of years, while the "get champion by year" endpoint returns the champion's name for a specified year. The "get champion data by name and year" endpoint delivers detailed statistics about a specific driver, including titles, age, team, and performance metrics.
Key fields include "year," "driver_name," "Titles," "Season," "Age," "Chassis," "Engine," "Tyres," "Poles," "Wins," "Podiums," "Fastest laps," "Points," and various percentage metrics. These fields provide comprehensive insights into each champion's performance and background.
The response data is structured in JSON format. Each endpoint returns an object with relevant fields. For example, the champion data includes driver statistics as key-value pairs, making it easy to parse and utilize in applications or analyses.
The "get all championship years" endpoint provides a list of years. The "get champion by year" endpoint offers the champion's name for a specific year. The "get champion data by name and year" endpoint includes detailed statistics about a driver, such as wins, points, and team information.
The "get champion by year" endpoint requires a "year" parameter, while the "get champion data by name and year" endpoint requires both "driver name" and "year" parameters. Users can customize requests by specifying these values to retrieve targeted data.
The F1 Title Holders API sources its data from official records of the Formula One World Drivers' Championship. Regular updates and checks against authoritative databases ensure the accuracy and reliability of the information provided.
Typical use cases include creating motorsport analysis platforms, developing data visualizations, and building fan applications that track historical performance and statistics of Formula One drivers and championships.
Users can parse the JSON responses to extract specific fields for analysis or display. For instance, developers can visualize trends in driver performance over the years or compare statistics between different champions using the detailed data provided.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key 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.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
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. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund