The Football World Cup API is a powerful tool that provides developers with access to detailed information about every World Cup tournament in history. Starting from the first tournament in 1930.
Using the Football World Cup API, developers can create applications that showcase the rich history of the World Cup. For example, a developer could create an application that displays the results of past World Cup tournaments, including the teams that competed, the scores of each match, and the eventual winners of the tournament. With access to data from every World Cup tournament, developers can create applications that provide a comprehensive look at the history of this iconic sporting event.
Overall, the Football World Cup API is an incredibly useful resource for developers looking to create applications that showcase the history and excitement of the World Cup. With access to comprehensive data from every tournament, developers can create engaging applications that keep fans informed and entertained.
It will receive parameters and provide you with a JSON.
Football History Applications: Developers can use the API to create applications that showcase the history of the World Cup. This can include displaying past tournament results, team and player statistics, and other relevant data.
News and Media Coverage: News outlets can use the API to retrieve data on current and past World Cup tournaments, which they can use to create news articles and coverage.
Statistics and Analysis: Analysts and statisticians can use the API to retrieve data on previous World Cup tournaments, which they can use to perform in-depth analysis and statistical modeling.
Social Media Applications: Social media platforms can use the API to create features that allow users to share updates and information about World Cup tournaments.
Coaching and Training Applications: Coaches and trainers can use the API to retrieve data on previous World Cup tournaments, which they can use to inform training and coaching strategies.
Educational Applications: Educational institutions can use the API to create educational materials and resources that teach students about the history and culture of the World Cup.
Tourism Applications: Tourism companies can use the API to create applications that provide information about World Cup tournaments and associated events, helping tourists plan their trips and activities.
Basic Plan: 500 API Calls.
Pro Plan: 1,000 API Calls.
Pro Plus Plan: 5,000 API Calls.
Elite Plan: 10,000 API Calls.
The Fetch World Cup By Host endpoint is a powerful feature of the Football World Cup API that allows developers to retrieve data on past World Cup tournaments based on the host country. By using this endpoint, developers can filter data to retrieve information on specific tournaments hosted by a particular country, providing a comprehensive look at that country's history with the tournament. This feature is particularly useful for developers creating applications that showcase the history of the World Cup, as it allows them to provide users with detailed information on tournaments hosted by a particular country.
Requiered Parameter: host
For example: Argentina
[{"id": 10, "year": 1978, "country": "Argentina", "winner": "Argentina", "winner_flag": "http://media.tekbunny.com/flags/svg/arg.svg", "runners_up": "Netherlands", "runners_up_flag": "http://media.tekbunny.com/flags/svg/nld.svg", "third": "Brazil", "third_flag": "http://media.tekbunny.com/flags/svg/bra.svg", "fourth": "Italy", "fourth_flag": "http://media.tekbunny.com/flags/svg/ita.svg", "goals_scored": 102, "qualified_teams": 16, "matches_played": 38, "attendance": 1545791, "golden_ball": "Mario Kempes", "golden_boot": "Mario Kempes", "golden_glove": "Ubaldo Fillol", "best_young_player": "Antonio Cabrini"}]
curl --location --request GET 'https://zylalabs.com/api/1736/football+world+cup+api/1350/fetch+world+cup+by+host&host=Required' --header 'Authorization: Bearer YOUR_API_KEY'
The Fetch World Cup By Year endpoint is a powerful feature of the Football World Cup API that allows developers to retrieve data on past World Cup tournaments based on the year in which they took place. By using this endpoint, developers can filter data to retrieve information on a specific tournament that occurred in a particular year.
Requiered Parameter: year
For example: 1930
{"id": 0, "year": 1930, "country": "Uruguay", "winner": "Uruguay", "winner_flag": "http://media.tekbunny.com/flags/svg/ury.svg", "runners_up": "Argentina", "runners_up_flag": "http://media.tekbunny.com/flags/svg/arg.svg", "third": "USA", "third_flag": "http://media.tekbunny.com/flags/svg/usa.svg", "fourth": "Yugoslavia", "fourth_flag": "http://media.tekbunny.com/flags/svg/no-image.png", "goals_scored": 70, "qualified_teams": 13, "matches_played": 18, "attendance": 590549, "golden_ball": "Jos\u00e9 Nasazzi", "golden_boot": "Guillermo Stabile", "golden_glove": "Enrique Ballestrero", "best_young_player": ""}
curl --location --request GET 'https://zylalabs.com/api/1736/football+world+cup+api/1351/fetch+world+cup+by+year&year=Required' --header 'Authorization: Bearer YOUR_API_KEY'
The Fetch World Cup By Winner endpoint is a useful feature of the Football World Cup API that allows developers to retrieve data on past World Cup tournaments based on the country that won the tournament. By using this endpoint, developers can filter data to retrieve information on tournaments won by a particular country, providing a comprehensive look at that country's history with the tournament.
Required Parameter: winner
For example: Germany
[{"id": 4, "year": 1954, "country": "Switzerland", "winner": "Germany", "winner_flag": "http://media.tekbunny.com/flags/svg/deu.svg", "runners_up": "Hungary", "runners_up_flag": "http://media.tekbunny.com/flags/svg/hun.svg", "third": "Austria", "third_flag": "http://media.tekbunny.com/flags/svg/aut.svg", "fourth": "Uruguay", "fourth_flag": "http://media.tekbunny.com/flags/svg/ury.svg", "goals_scored": 140, "qualified_teams": 16, "matches_played": 26, "attendance": 768607, "golden_ball": "Ferenc Pusk\u00e1s", "golden_boot": "Sandor Kocsis", "golden_glove": "Gyula Grosics", "best_young_player": ""}, {"id": 9, "year": 1974, "country": "Germany", "winner": "Germany", "winner_flag": "http://media.tekbunny.com/flags/svg/deu.svg", "runners_up": "Netherlands", "runners_up_flag": "http://media.tekbunny.com/flags/svg/nld.svg", "third": "Poland", "third_flag": "http://media.tekbunny.com/flags/svg/pol.svg", "fourth": "Brazil", "fourth_flag": "http://media.tekbunny.com/flags/svg/bra.svg", "goals_scored": 97, "qualified_teams": 16, "matches_played": 38, "attendance": 1865753, "golden_ball": "Johan Cruyff", "golden_boot": "Grzegorz Lato", "golden_glove": "Sepp Maier", "best_young_player": "Wladyslaw Zmuda"}, {"id": 13, "year": 1990, "country": "Italy", "winner": "Germany", "winner_flag": "http://media.tekbunny.com/flags/svg/deu.svg", "runners_up": "Argentina", "runners_up_flag": "http://media.tekbunny.com/flags/svg/arg.svg", "third": "Italy", "third_flag": "http://media.tekbunny.com/flags/svg/ita.svg", "fourth": "England", "fourth_flag": "http://media.tekbunny.com/flags/svg/eng.svg", "goals_scored": 115, "qualified_teams": 24, "matches_played": 52, "attendance": 2516215, "golden_ball": "Salvatore Schillaci", "golden_boot": "Salvatore Schillaci", "golden_glove": "Luis Gabelo Conejo", "best_young_player": "Robert Prosinecki"}, {"id": 19, "year": 2014, "country": "Brazil", "winner": "Germany", "winner_flag": "http://media.tekbunny.com/flags/svg/deu.svg", "runners_up": "Argentina", "runners_up_flag": "http://media.tekbunny.com/flags/svg/arg.svg", "third": "Netherlands", "third_flag": "http://media.tekbunny.com/flags/svg/nld.svg", "fourth": "Brazil", "fourth_flag": "http://media.tekbunny.com/flags/svg/bra.svg", "goals_scored": 171, "qualified_teams": 32, "matches_played": 64, "attendance": 3386810, "golden_ball": "Lionel Messi", "golden_boot": "James Rodriguez", "golden_glove": "Manuel Neuer", "best_young_player": "Paul Pogba"}]
curl --location --request GET 'https://zylalabs.com/api/1736/football+world+cup+api/1352/fetch+world+cup+by+winner&winner=Required' --header 'Authorization: Bearer YOUR_API_KEY'
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.
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:
9,713ms
Service Level:
100%
Response Time:
354ms
Service Level:
100%
Response Time:
2,207ms
Service Level:
100%
Response Time:
5,597ms
Service Level:
100%
Response Time:
2,623ms
Service Level:
100%
Response Time:
2,342ms
Service Level:
100%
Response Time:
1,256ms
Service Level:
99%
Response Time:
1,790ms
Service Level:
100%
Response Time:
3,797ms
Service Level:
100%
Response Time:
1,693ms
Service Level:
100%
Response Time:
346ms
Service Level:
90%
Response Time:
1,049ms
Service Level:
100%
Response Time:
3,114ms
Service Level:
100%
Response Time:
394ms
Service Level:
100%
Response Time:
939ms
Service Level:
100%
Response Time:
7,908ms
Service Level:
100%
Response Time:
429ms