The Tour De France Data API is designed to provide structured and easily accessible information about the Tour de France. Users can fetch a list of all available race years, query specific details about the winner and winning team, and get information about the second and third-place finishers for any given year. With a focus on flexibility and clarity, this API enables cycling enthusiasts, researchers, and developers to explore the rich history of the Tour de France without overwhelming responses. Users can filter data using parameters for efficient retrieval.
{"years":[1903,1904,1905,1906,1907,1908,1909,1910,1911,1912,1913,1914,1919,1920,1921,1922,1923,1924,1925,1926,1927,1928,1929,1930,1931,1932,1933,1934,1935,1936,1937,1938,1939,1947,1948,1949,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,2025]}
curl --location --request POST 'https://zylalabs.com/api/6036/tour+de+france+data+api/8138/get+available+race+years' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{"year":1903,"winner":"Garin, Maurice","winner_age":32,"nationality":"France","team":"La Fran\u00e7aise"}
curl --location --request POST 'https://zylalabs.com/api/6036/tour+de+france+data+api/8139/get+winner+and+team+by+year' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"year":"Required"}'
{"year":1903,"podium":[{"rider":"Lucien Pothier","time":"2hr 59min 21sec"},{"rider":"Fernand Augereau","time":"4hr 29min 24sec"}]}
curl --location --request POST 'https://zylalabs.com/api/6036/tour+de+france+data+api/8140/get+podium+results+by+year' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"year":"Required"}'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
You can retrieve data about available race years, winners, winning teams, and podium results for each edition of the Tour de France.
The API allows you to filter data using parameters for specific years, which enables efficient retrieval of information related to particular editions of the race.
Yes, the API provides detailed information about the second and third-place finishers for any given year of the Tour de France.
Absolutely! The Tour De France Data API is designed for cycling enthusiasts, researchers, and developers, offering structured and easily accessible information.
The API focuses on providing precise data access through year-based queries, allowing users to explore the history of the Tour de France without overwhelming responses.
The "get available race years" endpoint returns a list of years when the Tour de France was held. The "get winner and team by year" endpoint provides details about the race winner, including their name, age, nationality, and team. The "get podium results by year" endpoint returns the names and times of the top finishers for a specified year.
Key fields include "years" in the race years response, "winner," "winner_age," "nationality," and "team" in the winner response, and "podium" with rider names and times in the podium results response.
Responses are structured in JSON format. For example, the years response contains an array of years, while the winner response includes individual fields for the winner's details, and the podium results response contains an array of podium finishers with their respective times.
The "get available race years" endpoint provides a list of years. The "get winner and team by year" endpoint offers details about the winner and their team for a specific year. The "get podium results by year" endpoint gives the complete podium results, including second and third-place finishers.
The "get winner and team by year" and "get podium results by year" endpoints require a "year" parameter to specify which year's data to retrieve. Users can obtain valid years from the first endpoint.
Users can customize requests by specifying the year parameter in the winner and podium endpoints. This allows for targeted queries to retrieve information for specific editions of the Tour de France.
Typical use cases include historical research on the Tour de France, analysis of winning trends over the years, and development of applications or websites that showcase cycling statistics and records.
Data accuracy is maintained through careful curation from reliable historical records of the Tour de France. The API is designed to provide verified information, ensuring users receive accurate and trustworthy data.
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 1000 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 1000 requests per month, this header will display 1000.
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 3600, it means 3600 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 let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
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 trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
100%
Response Time:
3,149ms
Service Level:
100%
Response Time:
509ms
Service Level:
100%
Response Time:
4,608ms
Service Level:
100%
Response Time:
7,031ms
Service Level:
100%
Response Time:
683ms
Service Level:
100%
Response Time:
7,031ms
Service Level:
100%
Response Time:
607ms
Service Level:
100%
Response Time:
231ms
Service Level:
100%
Response Time:
381ms
Service Level:
100%
Response Time:
683ms