The Bundesliga Stats API is a RESTful service that delivers historical data of Germany’s top-tier football league — the Bundesliga. Designed for sports analysts, developers, and fans, the API enables access to detailed records of past champions, runners-up, number of titles by club, and historical league tables. It leverages structured endpoints that mirror the historical tables found on the official Wikipedia page. By providing individual endpoints for season results, team performances, and title counts, the API supports targeted data queries, filtering, and integration with sports analytics platforms.
[{"seasons":["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/6790/bundesliga+stats+api/10184/get+bundesliga+seasons' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
[{"season":"1983-1984","champion":"VfB Stuttgart","runner_up":"Hamburger SV","third_place":"SV Werder Bremen"},[]]
curl --location --request POST 'https://zylalabs.com/api/6790/bundesliga+stats+api/10185/get+bundesliga+podium+by+season' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"season":"Required"}'
[{"clubs":["FC Bayern M\u00fcnchen","Borussia M\u00f6nchengladbach","Borussia Dortmund","SV Werder Bremen","Hamburger SV","VfB Stuttgart","FC K\u00f6ln","FC Kaiserslautern","TSV 1860 M\u00fcnchen","Eintracht Braunschweig","FC N\u00fcrnberg","VfL Wolfsburg","Bayer 04 Leverkusen"]},[]]
curl --location --request POST 'https://zylalabs.com/api/6790/bundesliga+stats+api/10186/get+bundesliga+champions' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
[{"club":"FC Bayern M\u00fcnchen","total_titles":34,"years":"1969, 1972, 1973, 1974, 1980, 1981, 1985, 1986, 1987, 1989, 1990, 1994, 1997, 1999, 2000, 2001, 2003, 2005, 2006, 2008, 2010, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023, 2025"},[]]
curl --location --request POST 'https://zylalabs.com/api/6790/bundesliga+stats+api/10187/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 Bundesliga Stats API provides access to historical data about the German Bundesliga, including information on past champions, runners-up, the number of titles won by clubs, and historical league tables.
The API is designed for sports analysts, developers, and fans who are interested in accessing detailed records and statistics related to the Bundesliga football league.
You can query past champions by season through the API, which allows you to retrieve data on which teams won the league in specific years.
Yes, the data is extracted from official Bundesliga records, ensuring accuracy and reliability for users.
Yes, the API allows you to access statistics regarding the most successful clubs, including the total number of titles won by each club throughout Bundesliga history.
Each endpoint returns structured data related to the Bundesliga. For example, the "get bundesliga seasons" endpoint returns a list of all seasons, while "get bundesliga podium by season" provides details on the champion, runner-up, and third place for a specified season.
Key fields include "season," "champion," "runner_up," "third_place," and "total_titles." For instance, the "get title count by team" endpoint returns "club," "total_titles," and "years" when querying a specific team's title history.
The response data is organized in JSON format, typically as an array of objects. Each object contains relevant fields, such as season details or club statistics, making it easy to parse and utilize in applications.
Parameters vary by endpoint. For example, "get bundesliga podium by season" requires a specific season as input, while "get title count by team" needs a club name. Users can customize requests by providing these parameters.
Each endpoint offers distinct information: "get bundesliga seasons" lists all seasons, "get bundesliga champions" provides a list of winning clubs, and "get bundesliga podium by season" details the top three teams for a given season.
Users can integrate the returned data into sports analytics platforms or applications. For example, they can visualize trends in club performance over seasons or analyze the historical success of specific teams using the title counts.
The data is sourced from official Bundesliga records, ensuring high accuracy and reliability. This allows users to trust the statistics and historical information provided by the API.
Typical use cases include sports analytics, historical research, and fan engagement applications. Developers can create dashboards displaying club performance, or analysts can study trends in championship wins over the years.
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
Service Level:
100%
Response Time:
527ms
Service Level:
100%
Response Time:
2,572ms
Service Level:
100%
Response Time:
4,967ms
Service Level:
100%
Response Time:
53ms
Service Level:
100%
Response Time:
54ms
Service Level:
100%
Response Time:
56ms
Service Level:
100%
Response Time:
55ms
Service Level:
100%
Response Time:
16ms
Service Level:
100%
Response Time:
10,865ms
Service Level:
100%
Response Time:
10,044ms