The Premier League History API is designed to handle a specialized domain of sports data, specifically focusing on the history and statistics of the Premier League in England. It processes various types of data fields, including team histories, player records, and historical achievements. Key data structures include tables for historical top scorers, records, and classifications of historical performance by season.
{"seasons":["1888-89","1889-90","1890-91","1891-92","1892-93","1893-94","1894-95","1895-96","1896-97","1897-98","1898-99","1899-00","1900-01","1901-02","1902-03","1903-04","1904-05","1905-06","1906-07","1907-08","1908-09","1909-10","1910-11","1911-12","1912-13","1913-14","1914-15","1919-20","1920-21","1921-22","1922-23","1923-24","1924-25","1925-26","1926-27","1927-28","1928-29","1929-30","1930-31","1931-32","1932-33","1933-34","1934-35","1935-36","1936-37","1937-38","1938-39","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/6786/premier+league+history+api/10170/get+all+premier+league+seasons' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{"season":"1960-61","champion":"Tottenham Hotspur","runner_up":"Sheffield Wednesday","third_place":"Wolverhampton Wand."}
curl --location --request POST 'https://zylalabs.com/api/6786/premier+league+history+api/10171/get+premier+league+podium+by+season' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"season":"Required"}'
{"season":"2010-11","player_name":"Carlos T\u00e9vez","team":"Manchester City","total_goals":20}
curl --location --request POST 'https://zylalabs.com/api/6786/premier+league+history+api/10172/get+top+scorer+by+season' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"season":"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 Premier League History API provides access to a variety of historical data, including team performance, player achievements, historical top scorers, records, and classifications of performance by season.
To retrieve player statistics, you can use specific endpoints provided by the API that focus on player records. You will need to specify parameters such as the player's name or ID to get detailed statistics and achievements.
The Premier League History API focuses on historical data, which means it provides information that is static and not updated in real-time. However, it offers comprehensive records that reflect the history of the league up to the current date.
The "get all premier league seasons" endpoint returns a list of all Premier League seasons. The "get premier league podium by season" endpoint provides the champion, runner-up, and third place for a specified season. The "get top scorer by season" endpoint returns details about the top scorer, including the player's name, team, and total goals for a given season.
Key fields in the response data include "seasons" for the list of seasons, "season," "champion," "runner_up," and "third_place" for podium details, and "player_name," "team," and "total_goals" for top scorer information. These fields provide essential insights into historical performance.
The response data is organized in JSON format. For example, the podium endpoint returns an object with fields for the season and podium positions, while the top scorer endpoint includes player details. This structure allows for easy parsing and integration into applications.
The "get premier league podium by season" and "get top scorer by season" endpoints require a "season" parameter to specify which season's data to retrieve. Users must provide a valid season from the list obtained from the first endpoint.
The "get all premier league seasons" endpoint provides a comprehensive list of seasons. The "get premier league podium by season" endpoint offers information on the top three teams for a specific season, while the "get top scorer by season" endpoint details the leading goal scorer's performance for that season.
Users can utilize the returned data to analyze historical trends, compare team performances across seasons, and identify key players. For instance, by examining top scorers over multiple seasons, users can assess player consistency and impact on their teams.
Typical use cases include sports analytics, historical research, and fan engagement applications. Developers can create visualizations of team performances, generate reports on player achievements, or build trivia games based on historical Premier League data.
Data accuracy is maintained through rigorous sourcing from official Premier League records and historical databases. The API is designed to reflect verified statistics, ensuring users receive reliable information for their analyses and 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:
97%
Response Time:
722ms
Service Level:
100%
Response Time:
439ms
Service Level:
100%
Response Time:
1,953ms
Service Level:
100%
Response Time:
862ms
Service Level:
100%
Response Time:
862ms
Service Level:
100%
Response Time:
862ms
Service Level:
100%
Response Time:
862ms
Service Level:
100%
Response Time:
862ms
Service Level:
100%
Response Time:
6,162ms
Service Level:
100%
Response Time:
453ms
Free Sign Up
