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'
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 Football World Cup API REST 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 commitments. One click upgrade/downgrade or cancellation. No questions asked.
Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.
Prices are listed in USD. 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 with paying by card, just contact us at [email protected]
Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further
Prices are based on a recurring monthly subscription depending on the plan selected β plus overage fees applied when a developer exceeds a planβs quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.
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.
Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.
Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.
You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]
Service Level:
100%
Response Time:
354ms
Service Level:
100%
Response Time:
3,287ms
Service Level:
100%
Response Time:
2,887ms
Service Level:
100%
Response Time:
1,712ms
Service Level:
100%
Response Time:
1,256ms
Service Level:
100%
Response Time:
1,510ms
Service Level:
100%
Response Time:
1,668ms
Service Level:
100%
Response Time:
1,484ms
Service Level:
88%
Response Time:
870ms
Service Level:
100%
Response Time:
3,202ms
Service Level:
100%
Response Time:
819ms
Service Level:
100%
Response Time:
328ms
Service Level:
100%
Response Time:
8,675ms
Service Level:
100%
Response Time:
1,533ms
Service Level:
100%
Response Time:
1,969ms
Service Level:
100%
Response Time:
287ms
Service Level:
100%
Response Time:
857ms