The FIFA World Cup Finals Info API delivers structured and filtered access to FIFA World Cup Finals data, sourced from official records. It’s designed for developers and data analysts who need to integrate or analyze football history data programmatically. The API is organized into endpoints for accessing different aspects of each final match: years, match outcomes (winner, runner-up, and score), and additional details (venue, attendance, referees, etc.). With parameterized queries (e.g., filtering by year), users can fetch only the relevant information they need, optimizing performance and usability.
[
{
"year": [
1930,
1934,
1938,
1950,
1954,
1958,
1962,
1966,
1970,
1974,
1978,
1982,
1986,
1990,
1994,
1998,
2002,
2006,
2010,
2014,
2018,
2022,
2026
]
}
]
curl --location --request POST 'https://zylalabs.com/api/8827/fifa+world+cup+finals+info+api/15540/get+all+years' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
[
{
"year": 2022,
"winner": "Argentina",
"runner_up": "France",
"score": "3–3 (4–2 pen.)"
}
]
curl --location --request POST 'https://zylalabs.com/api/8827/fifa+world+cup+finals+info+api/15545/get+finals+result+by+name' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"year":"Required"}'
[
{
"Year": 2022,
"Winners": "Argentina",
"Score": "3–3 (4–2 pen.)",
"Runners-up": "France",
"Venue": "Lusail Stadium",
"Location": "Lusail, Qatar",
"Attendance": 88966
}
]
curl --location --request POST 'https://zylalabs.com/api/8827/fifa+world+cup+finals+info+api/15548/get+finals+details+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 commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The FIFA World Cup Finals Info API provides access to historical data including match years, winners, runners-up, scores, venues, attendance, and referees for each final match.
The API returns data in a structured format, typically JSON, which allows for easy integration and manipulation in various programming environments.
Developers can use the API to create applications that display historical World Cup data, analyze trends over the years, or build interactive football-related websites and tools.
Each match record includes fields such as year, winner, runner-up, score, venue, attendance, and referee details, providing comprehensive insights into each final.
The API supports parameterized queries, allowing users to filter data by specific years or other criteria, enabling efficient retrieval of only the information needed.
This endpoint returns the winner, runner-up, and score for a specified FIFA World Cup Final year. For example, a request for 2022 yields data like "winner: Argentina," "runner-up: France," and "score: 3–3 (4–2 pen.)."
This endpoint provides comprehensive details about a specific final match, including the year, winner, score, runner-up, venue, location, and attendance, allowing for in-depth analysis of that match.
The API responses are structured in JSON format, with each endpoint returning an array of objects. Each object contains key-value pairs representing specific data fields, making it easy to parse and utilize in applications.
This endpoint requires a single parameter: the year of the final match you want to retrieve details for. You can obtain valid years from the "get all years" endpoint.
Users can customize requests by specifying the year parameter in the "get finals result by name" and "get finals details by year" endpoints, allowing for targeted retrieval of match data relevant to their needs.
Key fields include "year," "winner," "runner-up," "score," "venue," "location," and "attendance." These fields provide essential insights into each World Cup final match.
The "get all years" endpoint returns a list of all years in which FIFA World Cup Finals were held, enabling users to easily identify the historical timeline of the tournament.
The API sources its data from official FIFA records, ensuring high accuracy and reliability. Regular updates and quality checks are implemented to maintain data integrity.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
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.
Service Level:
100%
Response Time:
54ms
Service Level:
100%
Response Time:
58ms
Service Level:
100%
Response Time:
67ms
Service Level:
100%
Response Time:
2,475ms
Service Level:
100%
Response Time:
4,312ms
Service Level:
100%
Response Time:
2,467ms
Service Level:
100%
Response Time:
299ms
Service Level:
100%
Response Time:
6,589ms
Service Level:
100%
Response Time:
106ms
Service Level:
100%
Response Time:
3,078ms