The Serie A Stats API delivers organized data about the history of Serie A champions, sourced from the historical records of Italy’s top football division. It allows developers and football enthusiasts to programmatically access information about each championship season, the clubs that have won, the number of titles each club holds, and performance trends over time. The API is designed with a RESTful architecture, supporting filtered queries and statistical insights. It’s ideal for applications related to sports analytics, visualization, and trivia.
{"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/6788/serie+a+stats+api/10176/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/6788/serie+a+stats+api/10177/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/6788/serie+a+stats+api/10178/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/6788/serie+a+stats+api/10179/get+title+count+by+team' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"club":"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 Serie A Stats 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 Stats 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 Stats 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.
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 1,000 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 1,000 requests per month, this header will display 1,000.
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 3,600, it means 3,600 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 give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
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 free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
6,526ms
Service Level:
100%
Response Time:
6,526ms
Service Level:
100%
Response Time:
16,590ms
Service Level:
100%
Response Time:
6,526ms
Service Level:
100%
Response Time:
6,526ms
Service Level:
100%
Response Time:
655ms
Service Level:
100%
Response Time:
3,852ms
Service Level:
100%
Response Time:
12,589ms
Service Level:
100%
Response Time:
14,892ms
Service Level:
100%
Response Time:
14,892ms