This API is a RESTful API that exposes official ATP Tour statistics in a developer-friendly format. It covers datasets like player profiles, match stats, rankings, win/loss records, and head-to-head comparisons. Each dataset is served via dedicated endpoints supporting query parameters. This API empowers developers, analysts, and sports enthusiasts to build tennis applications, visualizations, and predictive models without scraping the ATP website.
{
"ATP_Serve_Leaders": {
"players": [
{
"player_name": "Giovanni Mpetshi Perricard"
},
{
"player_name": "Alexander Zverev"
},
{
"player_name": "Matteo Berrettini"
},
{
"player_name": "Taylor Fritz"
},
{
"player_name": "Jannik Sinner"
},
{
"player_name": "Ben Shelton"
},
{
"player_name": "Hubert Hurkacz"
},
{
"player_name": "Brandon Nakashima"
},
{
"player_name": "Felix Auger-Aliassime"
},
{
"player_name": "Tallon Griekspoor"
},
{
"player_name": "Carlos Alcaraz"
},
{
"player_name": "Quentin Halys"
},
{
"player_name": "Jack Draper"
},
{
"player_name": "Zhizhen Zhang"
},
{
"player_name": "Ugo Humbert"
},
{
"player_name": "Stefanos Tsitsipas"
},
{
"player_name": "Gabriel Diallo"
},
{
"player_name": "Sebastian Korda"
},
{
"player_name": "Lorenzo Sonego"
},
{
"player_name": "Jakub Mensik"
},
{
"player_name": "Nicolas Jarry"
},
{
"player_name": "Jiri Lehecka"
},
{
"player_name": "Andrey Rublev"
},
{
"player_name": "Casper Ruud"
},
{
"player_name": "Holger Rune"
},
{
"player_name": "Arthur Rinderknech"
},
{
"player_name": "Karen Khachanov"
},
{
"player_name": "Alexei Popyrin"
},
{
"player_name": "Grigor Dimitrov"
},
{
"player_name": "Gael Monfils"
},
{
"player_name": "Frances Tiafoe"
},
{
"player_name": "Lorenzo Musetti"
},
{
"player_name": "Arthur Fils"
},
{
"player_name": "Alexander Bublik"
},
{
"player_name": "Jordan Thompson"
},
{
"player_name": "Alex Michelsen"
},
{
"player_name": "Juncheng Shang"
},
{
"player_name": "Aleksandar Vukic"
},
{
"player_name": "Aleksandar Kovacevic"
},
{
"player_name": "Tommy Paul"
},
{
"player_name": "Mattia Bellucci"
},
{
"player_name": "Roman Safiullin"
},
{
"player_name": "Laslo Djere"
},
{
"player_name": "Danil Medvedev"
},
{
"player_name": "Tomas Martin Etcheverry"
},
{
"player_name": "Denis Shapovalov"
},
{
"player_name": "Nuno Borges"
},
{
"player_name": "Miomir Kecmanovic"
}
]
}
}
curl --location --request POST 'https://zylalabs.com/api/9099/global+tennis+records+analytics+api/16474/get+atp+ranking' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{
"player_stats": {
"player_name": "Alexander Zverev",
"rank": 3,
"aces_per_match": 8.5,
"first_serve_percentage": 69.8,
"first_serve_points_won_percentage": 76.6,
"second_serve_points_won_percentage": 55,
"service_games_won_percentage": 89,
"double_faults_per_match": 2.3
}
}
curl --location --request POST 'https://zylalabs.com/api/9099/global+tennis+records+analytics+api/16479/get+stats+by+player' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"player":"Required"}'
{
"ATP_Return_Leaders": [
{
"player_name": "Alex de Minaur"
},
{
"player_name": "Carlos Alcaraz"
},
{
"player_name": "Jannik Sinner"
},
{
"player_name": "Tommy Paul"
},
{
"player_name": "Francisco Cerundolo"
},
{
"player_name": "Alejandro Davidovich Fokina"
},
{
"player_name": "David Goffin"
},
{
"player_name": "Sebastian Baez"
},
{
"player_name": "Jack Draper"
},
{
"player_name": "Mariano Navone"
},
{
"player_name": "Lorenzo Musetti"
},
{
"player_name": "Alexander Zverev"
},
{
"player_name": "Novak Djokovic"
},
{
"player_name": "Tomas Machac"
},
{
"player_name": "Laslo Djere"
},
{
"player_name": "Cameron Norrie"
},
{
"player_name": "Karen Khachanov"
},
{
"player_name": "Denis Shapovalov"
},
{
"player_name": "Hugo Gaston"
},
{
"player_name": "Jaume Munar"
},
{
"player_name": "Matteo Arnaldi"
},
{
"player_name": "Nuno Borges"
},
{
"player_name": "Grigor Dimitrov"
},
{
"player_name": "Roberto Carballes Baena"
},
{
"player_name": "Alexander Shevchenko"
},
{
"player_name": "Alexandre Muller"
},
{
"player_name": "Holger Rune"
},
{
"player_name": "Arthur Fils"
},
{
"player_name": "Pedro Martinez"
},
{
"player_name": "Roberto Bautista Agut"
},
{
"player_name": "Alex Michelsen"
},
{
"player_name": "Corentin Moutet"
},
{
"player_name": "Flavio Cobolli"
},
{
"player_name": "Juncheng Shang"
},
{
"player_name": "Rinky Hijikata"
},
{
"player_name": "Taylor Fritz"
},
{
"player_name": "Andrey Rublev"
},
{
"player_name": "Marcos Giron"
},
{
"player_name": "Jakub Mensik"
},
{
"player_name": "Learner Tien"
},
{
"player_name": "Frances Tiafoe"
},
{
"player_name": "Jiri Lehecka"
},
{
"player_name": "Ugo Humbert"
},
{
"player_name": "Casper Ruud"
},
{
"player_name": "Sebastian Korda"
},
{
"player_name": "Daniel Altmaier"
},
{
"player_name": "Roman Safiullin"
},
{
"player_name": "Adrian Mannarino"
},
{
"player_name": "Zizou Bergs"
}
]
}
curl --location --request POST 'https://zylalabs.com/api/9099/global+tennis+records+analytics+api/16484/get+rank+by+name' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"name":"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 Global Tennis Records Analytics API provides access to a variety of data types, including player profiles, match statistics, player rankings, win/loss records, and head-to-head comparisons.
The API delivers data in a RESTful format, typically in JSON, which is easy to parse and integrate into applications. Each dataset is served via dedicated endpoints that support query parameters for filtering.
Developers can use the Global Tennis Records Analytics API to create tennis-related applications, such as performance analytics tools, player comparison features, ranking visualizations, and predictive models for match outcomes.
The core value proposition of the Global Tennis Records Analytics API is to provide official ATP Tour statistics in a developer-friendly format, enabling users to access rich data without the need for web scraping, thus facilitating the development of innovative tennis applications.
The API includes fields such as player names, match scores, tournament details, and ranking points. The output format is primarily JSON, which allows for structured data retrieval, making it easy to integrate into various applications.
This endpoint returns a list of tennis players ranked in the ATP Serve Leaders category. Each entry includes the player's name, allowing users to identify top performers in serving statistics.
The response includes fields such as player name, rank, aces per match, first serve percentage, and service games won percentage, providing detailed insights into a player's serving performance.
The response is structured as a JSON object containing an array of players, each represented by their name. This format allows for easy parsing and integration into applications for further analysis.
Users can specify the player's name to retrieve specific statistics. This customization allows for targeted data requests, focusing on individual player performance metrics.
This endpoint provides a list of players ranked in the ATP Under Pressure Leaders category, highlighting those who excel in high-stakes situations during matches, which can be crucial for performance analysis.
Users can analyze individual player statistics such as serve rating and break points saved percentage to assess performance trends, compare players, or develop predictive models for match outcomes.
The API sources its data directly from official ATP statistics, ensuring high accuracy. Regular updates and validation processes are implemented to maintain data integrity and reliability.
Typical use cases include developing analytics dashboards, creating player comparison tools, generating visualizations for match statistics, and building predictive models for tournament outcomes based on player performance data.
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used 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.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
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, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
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.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
592ms
Service Level:
100%
Response Time:
8,434ms
Service Level:
100%
Response Time:
1,138ms
Service Level:
100%
Response Time:
464ms
Service Level:
100%
Response Time:
2,914ms
Service Level:
100%
Response Time:
3,442ms
Service Level:
100%
Response Time:
692ms
Service Level:
100%
Response Time:
15,224ms
Service Level:
100%
Response Time:
9,827ms
Service Level:
100%
Response Time:
1,732ms
Service Level:
100%
Response Time:
620ms
Service Level:
100%
Response Time:
73ms
Service Level:
100%
Response Time:
8,667ms
Service Level:
100%
Response Time:
1,396ms
Service Level:
100%
Response Time:
248ms
Service Level:
100%
Response Time:
9,212ms
Service Level:
100%
Response Time:
57ms
Service Level:
100%
Response Time:
233ms
Service Level:
100%
Response Time:
221ms
Service Level:
100%
Response Time:
19ms