The Football Matches API is a powerful resource for developers who need access to a vast amount of data on football matches. This API offers a variety of features, including historical match data, live match scores, match statistics, lineup information, and more. With this API, developers can easily retrieve detailed information on a wide range of matches from multiple leagues.
One of the key benefits of the Football Matches API is its ability to provide real-time updates on live matches. This feature allows developers to create applications that display live match scores and other statistics, which can be updated in real-time as the game progresses. Additionally, the API also provides access to historical match data, allowing developers to analyze past matches and gain insights into team performance and other trends.
Another advantage of the Football Matches API is its flexibility. Developers can easily integrate this API into their applications, regardless of the programming language or platform they are using. Additionally, the API offers a range of customization options, allowing developers to tailor the data they receive to meet their specific needs.
Overall, the Football Matches API is an ideal resource for developers who are building sports-related applications or who need access to detailed information on football matches. With its comprehensive data, real-time updates, and flexible integration options, this API can help developers create powerful and informative applications that meet the needs of their users.
It will receive parameters and provide you with a JSON.
Live match score updates: Developers can use the API to retrieve real-time updates on live match scores and display them in their application.
Betting and prediction applications: The API can be used to provide data on match statistics and historical performance, helping developers to create betting and prediction applications.
Fantasy sports applications: The API can be used to retrieve lineup information, helping developers to create fantasy sports applications.
Sports news websites: The API can be used to retrieve match information and statistics for use in sports news articles and features.
Sports analysis tools: The API can be used to retrieve historical match data and perform statistical analysis to gain insights into team performance and other trends.
Mobile applications: Developers can use the API to create mobile applications that provide match information and updates on-the-go.
Social media integration: The API can be used to retrieve match information and statistics for use in social media posts and updates.
Television broadcasts: The API can be used to provide live match score updates and other information for use in television broadcasts.
Sports merchandise websites: The API can be used to retrieve information on team performance and statistics, which can be used to inform merchandise sales.
Sports analytics services: The API can be used to provide data to sports analytics services, which can be used to inform decision-making in sports management and coaching.
Basic Plan: 10,000 API Calls.
Pro Plan: 25,000 API Calls.
Pro Plus Plan: 50,000 API Calls.
Premium Plan: 300,000 API Calls.
The Fetch Matches endpoint is a powerful feature of the Football Matches API that allows developers to retrieve all matches for a particular date. By default, this endpoint returns matches for the current date, and the timezone for matches is set to GMT+1. This endpoint can be used in a variety of ways, such as to display all matches on a particular day and to retrieve historical match data. With its flexible customization options, the Fetch Matches endpoint is an essential resource for developers who need comprehensive data on football matches.
Fetch Matches - Endpoint Features
Object | Description |
---|---|
date |
[Optional] Format must be: YYYY-MM-DD. For example: 2023-03-08 |
[]
curl --location --request GET 'https://zylalabs.com/api/1735/football+matches+api/1346/fetch+matches' --header 'Authorization: Bearer YOUR_API_KEY'
The Fetch Match Info endpoint is a key feature of the Football Matches API that allows developers to retrieve detailed information on a particular football match by providing the match ID. This endpoint provides comprehensive data on match details, such as the stadium location, match officials, and other relevant information. The timezone for matches is set to GMT+1, ensuring accurate and consistent data for developers. This endpoint is particularly useful for creating sports news and analysis websites, as well as for sports betting and prediction applications. With its comprehensive data and flexibility, the Fetch Match Info endpoint is an essential resource for developers working with football match data.
Required Parameter: match_id
For example: 844286
{"matchEvents":[],"venue":"","referee":"","spectators":""}
curl --location --request GET 'https://zylalabs.com/api/1735/football+matches+api/1347/fetch+match+info&match_id=Required' --header 'Authorization: Bearer YOUR_API_KEY'
The Fetch Match Stats endpoint is a valuable feature of the Football Matches API that allows developers to retrieve detailed statistics on a particular football match by providing the match ID. This endpoint provides comprehensive data on match statistics. The timezone for matches is set to GMT+1, ensuring accurate and consistent data for developers. This endpoint is particularly useful for creating sports analysis and prediction applications, as well as for generating sports betting odds. With its detailed statistics and flexibility, the Fetch Match Stats endpoint is an essential resource for developers working with football match data.
Required Parameter: match_id
For example: 844286
{"matchInfo":{"homeTeamName":"Bayern Munich","homeTeamScore":"2","awayTeamName":"Paris Saint-Germain","awayTeamScore":"0"},"statistics":[{"label":"Shots on target","homeTeam":"5","awayTeam":"4"},{"label":"Shots off target","homeTeam":"2","awayTeam":"2"},{"label":"Blocked Shots","homeTeam":"4","awayTeam":"5"},{"label":"Possession (%)","homeTeam":"48","awayTeam":"52"},{"label":"Corner Kicks","homeTeam":"4","awayTeam":"6"},{"label":"Offsides","homeTeam":"3","awayTeam":"0"},{"label":"Fouls","homeTeam":"9","awayTeam":"6"},{"label":"Throw ins","homeTeam":"18","awayTeam":"26"},{"label":"Yellow cards","homeTeam":"0","awayTeam":"1"},{"label":"Crosses","homeTeam":"18","awayTeam":"15"},{"label":"Counter attacks","homeTeam":"6","awayTeam":"3"},{"label":"Goalkeeper saves","homeTeam":"4","awayTeam":"3"},{"label":"Goal kicks","homeTeam":"6","awayTeam":"4"},{"label":"Treatments","homeTeam":"0","awayTeam":"4"}]}
curl --location --request GET 'https://zylalabs.com/api/1735/football+matches+api/1348/fetch+match+stats&match_id=Required' --header 'Authorization: Bearer YOUR_API_KEY'
The Fetch Match Line Up endpoint is a valuable feature of the Football Matches API that allows developers to retrieve the lineup for a particular football match by providing the match ID. This endpoint provides detailed information on the starting lineup, as well as the substitutes for each team. The timezone for matches is set to GMT+1, ensuring accurate and consistent data for developers. This endpoint is particularly useful for creating fantasy sports applications, as well as for providing detailed match information for sports news and analysis websites. With its comprehensive data and flexibility, the Fetch Match Line Up endpoint is an essential resource for developers working with football match data.
Required Parameter: match_id
For example: 844286
{"homeTeamName":"Bayern Munich","homeTeamFormation":"4-2-3-1","homeLineUp":[{"number":"27","name":"Yann Sommer","actions":[]},{"number":"44","name":"Josip Stanisic","actions":[]},{"number":"2","name":"Dayot Upamecano","actions":[]},{"number":"4","name":"Matthijs De Ligt","actions":[]},{"number":"19","name":"Alphonso Davies","actions":[]},{"number":"6","name":"Joshua Kimmich","actions":[]},{"number":"8","name":"Leon Goretzka","actions":[]},{"number":"11","name":"Kingsley Coman","actions":["FootballSubOut"]},{"number":"25","name":"Thomas Muller","actions":["FootballSubOut"]},{"number":"42","name":"Jamal Musiala","actions":["FootballSubOut"]},{"number":"13","name":"Eric Maxim Choupo-Moting","actions":["FootballGoal","FootballSubOut"]}],"homeSubstitutes":[{"name":"Sven Ulreich","actions":[]},{"name":"Bouna Sarr","actions":[]},{"name":"Joao Cancelo","actions":["FootballSubIn"]},{"name":"Daley Blind","actions":[]},{"name":"Noussair Mazraoui","actions":[]},{"name":"Leroy Sane","actions":["FootballSubIn"]},{"name":"Paul Wanner","actions":[]},{"name":"Ryan Gravenberch","actions":[]},{"name":"Serge Gnabry","actions":["FootballGoal","FootballSubIn"]},{"name":"Sadio Mane","actions":["FootballSubIn"]},{"name":"Mathys Tel","actions":[]},{"name":"Arijon Ibrahimovic","actions":[]}],"homeSubstitutions":[{"subTime":"68'","subIn":"Eric Maxim Choupo-Moting","subOut":"Leroy Sane"},{"subTime":"82'","subIn":"Jamal Musiala","subOut":"Sadio Mane"},{"subTime":"86'","subIn":"Kingsley Coman","subOut":"Serge Gnabry"},{"subTime":"86'","subIn":"Thomas Muller","subOut":"Joao Cancelo"},{"subTime":""}],"homeTeamCoach":"Julian Nagelsmann","awayTeamName":"Paris Saint-Germain","awayTeamFormation":"3-5-2","awayLineUp":[{"number":"7","name":"Kylian Mbappe","actions":[]},{"number":"30","name":"Lionel Messi","actions":[]},{"number":"25","name":"Nuno Mendes","actions":["FootballSubOut"]},{"number":"8","name":"Fabian Ruiz","actions":["FootballSubOut"]},{"number":"6","name":"Marco Verratti","actions":[]},{"number":"17","name":"Vitinha","actions":["FootballSubOut"]},{"number":"2","name":"Achraf Hakimi","actions":["FootballYellowCard"]},{"number":"5","name":"Marquinhos","actions":["FootballSubOut"]},{"number":"4","name":"Sergio Ramos","actions":[]},{"number":"15","name":"Danilo Pereira","actions":[]},{"number":"99","name":"Gianluigi Donnarumma","actions":[]}],"awaySubstitutes":[{"name":"Sergio Rico","actions":[]},{"name":"Alexandre Letellier","actions":[]},{"name":"Juan Bernat","actions":["FootballSubIn"]},{"name":"Nordi Mukiele","actions":["FootballSubIn"]},{"name":"Timothee Pembele","actions":[]},{"name":"El Chadaille Bitshiabu","actions":["FootballSubIn"]},{"name":"Renato Sanches","actions":[]},{"name":"Carlos Soler","actions":[]},{"name":"Warren Zaire Emery","actions":["FootballSubIn"]},{"name":"Ismael Gharbi","actions":[]},{"name":"Hugo Ekitike","actions":["FootballSubIn"]},{"name":"","actions":[]}],"awaySubstitutions":[{"subTime":"36'","subIn":"Marquinhos","subOut":"Nordi Mukiele"},{"subTime":"46'","subIn":"Nordi Mukiele","subOut":"El Chadaille Bitshiabu"},{"subTime":"76'","subIn":"Fabian Ruiz","subOut":"Warren Zaire Emery"},{"subTime":"81'","subIn":"Vitinha","subOut":"Hugo Ekitike"},{"subTime":"81'","subIn":"Nuno Mendes","subOut":"Juan Bernat"}],"awayTeamCoach":"Christophe Galtier"}
curl --location --request GET 'https://zylalabs.com/api/1735/football+matches+api/1349/fetch+match+line+up&match_id=Required' --header 'Authorization: Bearer YOUR_API_KEY'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
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 1000 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 1000 requests per month, this header will display 1000.
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 3600, it means 3600 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 let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
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 trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
100%
Response Time:
2,623ms
Service Level:
100%
Response Time:
900ms
Service Level:
100%
Response Time:
3,114ms
Service Level:
100%
Response Time:
1,256ms
Service Level:
100%
Response Time:
2,342ms
Service Level:
100%
Response Time:
6,162ms
Service Level:
100%
Response Time:
394ms
Service Level:
100%
Response Time:
354ms
Service Level:
100%
Response Time:
1,969ms
Service Level:
100%
Response Time:
247ms
Service Level:
100%
Response Time:
8,675ms
Service Level:
100%
Response Time:
1,693ms
Service Level:
100%
Response Time:
5,141ms
Service Level:
100%
Response Time:
287ms
Service Level:
100%
Response Time:
272ms
Service Level:
100%
Response Time:
1,176ms
Service Level:
100%
Response Time:
4,876ms