{"seasons":["1929-30","1930-31","1931-32","1932-33","1933-34","1934-35","1935-36","1936-37","1937-38","1938-39","1939-40","1940-41","1941-42","1942-43","1945-46","1946-47","1947-48","1948-49","1949-50","1950-51","1951-52","1952-53","1953-54","1954-55","1955-56","1956-57","1957-58","1958-59","1959-60","1960-61","1961-62","1962-63","1963-64","1964-65","1965-66","1966-67","1967-68","1968-69","1969-70","1970-71","1971-72","1972-73","1973-74","1974-75","1975-76","1976-77","1977-78","1978-79","1979-80","1980-81","1981-82","1982-83","1983-84","1984-85","1985-86","1986-87","1987-88","1988-89","1989-90","1990-91","1991-92","1992-93","1993-94","1994-95","1995-96","1996-97","1997-98","1998-99","1999-00","2000-01","2001-02","2002-03","2003-04","2004-05","2005-06","2006-07","2007-08","2008-09","2009-10","2010-11","2011-12","2012-13","2013-14","2014-15","2015-16","2016-17","2017-18","2018-19","2019-20","2020-21","2021-22","2022-23","2023-24","2024-25"]}
curl --location --request POST 'https://zylalabs.com/api/7093/serie+a+data+api/11076/get+seria+a+seasons' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{"season":"1985-86","champion":"Juventus F. C.","runner_up":"A. S. Roma","third_place":"S. S. C. Napoli"}
curl --location --request POST 'https://zylalabs.com/api/7093/serie+a+data+api/11077/get+serie+a+podium+by+season' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"season":"Required"}'
{"clubs":["Juventus F. C.","F. C. Internazionale","A. C. Milan","Genoa F.C.","F.C. Pro Vercelli 1892","Bologna F. C.","Torino F. C.","A. S. Roma","S. S. C. Napoli","A. C. F. Fiorentina","S. S. Lazio","F.C. Casale","A.S.D. Novese","Cagliari Calcio","Hellas Verona F. C.","U. C. Sampdoria"]}
curl --location --request POST 'https://zylalabs.com/api/7093/serie+a+data+api/11078/get+serie+a+champions' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{"club":"Juventus F. C.","total_titles":36,"years":[1905,1926,1931,1932,1933,1934,1935,1950,1952,1958,1960,1961,1967,1972,1973,1975,1977,1978,1981,1982,1984,1986,1995,1997,1998,2002,2003,2012,2013,2014,2015,2016,2017,2018,2019,2020]}
curl --location --request POST 'https://zylalabs.com/api/7093/serie+a+data+api/11079/get+title+count+by+team' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"club":"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 Serie A Data 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 🎉)
Trusted by leading companies
The Serie A Data API provides comprehensive statistical data about the history of Serie A, including information on championship seasons, clubs that have won titles, the number of titles held by each club, and performance trends over time.
The API supports filtered queries, allowing developers to specify parameters to retrieve specific data, such as particular seasons, clubs, or performance metrics, making it easier to access relevant information.
Yes, the Serie A Data API is designed for sports analytics, visualization, and trivia applications, providing organized data that can be easily integrated into various projects related to football statistics.
The Serie A Data API is built with a RESTful architecture, which allows for easy integration and interaction with the API using standard HTTP methods.
Each endpoint returns specific statistical data related to Serie A. For example, "get seria a seasons" returns a list of all seasons, "get serie a podium by season" provides podium details for a specific season, while "get title count by team" returns the total titles won by a specified club along with the years they were won.
Key fields include "seasons" in the seasons endpoint, "champion," "runner_up," and "third_place" in the podium endpoint, and "total_titles" and "years" in the title count endpoint. These fields provide essential information about Serie A history and club performance.
The "get serie a podium by season" and "get title count by team" endpoints require a season or club parameter, respectively. Users must specify these parameters to retrieve relevant data, ensuring targeted queries for specific information.
Response data is structured in JSON format, with clear key-value pairs. For instance, the podium endpoint returns a JSON object containing the season and podium positions, while the title count endpoint includes the club name, total titles, and the years they were won.
Typical use cases include sports analytics, historical research, and trivia applications. Developers can use the data to create visualizations, analyze club performance trends, or build engaging trivia games based on Serie A history.
Data is sourced from historical records of Serie A, ensuring reliability. Regular updates and quality checks are implemented to maintain accuracy, allowing users to trust the information provided by the API for their applications.
Users can parse the JSON responses to extract relevant information for their applications. For example, they can display championship winners, analyze title counts over time, or visualize podium placements for specific seasons, enhancing user engagement.
Users can expect consistent data patterns, such as lists of seasons or clubs in array format and structured objects for podium and title count details. This uniformity simplifies data handling and integration into various applications.
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