TennisExplorer APItennisexplorer.com ↗
Access ATP/WTA tournament schedules, player profiles, rankings, and today's match data from TennisExplorer via a structured JSON API.
What is the TennisExplorer API?
The TennisExplorer API exposes 8 endpoints covering ATP and WTA tennis data including live-week schedules, today's match listings, player profiles, and the full ATP season calendar. The get_atp_rankings endpoint returns the current top-50 men's singles rankings with rank, points, country, and a slug you can pass directly into get_player_profile to retrieve birthdate, country, and recent match history.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/b78070b1-9399-4616-9b1a-6b6ce1a05a66/get_weekly_tournaments' \ -H 'X-API-Key: $PARSE_API_KEY'
Fetch all tournaments scheduled for the current week, categorized by tour (ATP/WTA) and level (Main/Lower). Returns a single schedule object with four arrays. Each tournament entry includes the name, URL, and number of scheduled matches.
No input parameters required.
{
"type": "object",
"fields": {
"atp_main": "array of ATP main-level tournament objects",
"wta_main": "array of WTA main-level tournament objects",
"atp_lower": "array of ATP lower-level tournament objects",
"wta_lower": "array of WTA lower-level tournament objects"
},
"sample": {
"data": {
"atp_main": [
{
"url": "https://www.tennisexplorer.com/stuttgart/2026/atp-men/",
"name": "Stuttgart",
"match_count": 10
}
],
"wta_main": [
{
"url": "https://www.tennisexplorer.com/queen-s-club/2026/wta-women/",
"name": "Queen's Club",
"match_count": 9
}
],
"atp_lower": [
{
"url": "https://www.tennisexplorer.com/ilkley-challenger/2026/atp-men/",
"name": "Ilkley challenger",
"match_count": 12
}
],
"wta_lower": [
{
"url": "https://www.tennisexplorer.com/ilkley-wta/2026/wta-women/",
"name": "Ilkley WTA",
"match_count": 13
}
]
},
"status": "success"
}
}About the TennisExplorer API
Tournament Schedules and Season Calendar
get_weekly_tournaments returns four arrays in a single call — atp_main, wta_main, atp_lower, and wta_lower — each containing tournament name, URL, and match count for the current week. If you only need one tier, get_atp_main_tournaments and get_atp_lower_level_tournaments offer focused responses; the lower-level variant returns up to 3 tournaments sorted by ascending match count, which is useful for identifying the smallest events on the circuit. For season-level planning, get_atp_season_calendar accepts a year parameter (e.g. '2025') and an optional level filter (main, lower, or all), and returns one record per tournament with start_date (ISO format), surface, prize_money as displayed on the site, and level.
Match Listings and Player Data
get_today_matches accepts an optional tour_type filter with four accepted values — atp-single, wta-single, atp-double, wta-double — and returns each match with tournament name, scheduled time, and player names. Player lookup starts with search_player, which takes a name query (e.g. 'Alcaraz' or 'Sinner') and returns matching names, profile URLs, and slugs. The slug feeds directly into get_player_profile, which returns name, country, birthdate, slug, and a recent_matches array with tournament, round, and date fields.
Rankings
get_atp_rankings returns the current top-50 ATP men's singles rankings. Each entry includes rank, player name, country, points, and a slug compatible with get_player_profile. Rankings reflect the current standings as published on TennisExplorer and are not versioned or historical within this API.
Coverage Notes
The API covers ATP men's data most thoroughly — rankings, season calendars, and lower-level tournament breakdowns are ATP-specific. WTA data is accessible through get_weekly_tournaments and get_today_matches with tour filtering, but there is no dedicated WTA rankings or WTA season calendar endpoint at this time.
The TennisExplorer API is a managed, monitored endpoint for tennisexplorer.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when tennisexplorer.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official tennisexplorer.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a weekly tennis dashboard showing all ATP and WTA tournaments and their scheduled match counts.
- Track today's ATP singles or doubles matches by filtering
get_today_matcheswithtour_type. - Look up a player's country, birthdate, and recent match history using
search_playerfollowed byget_player_profile. - Identify the smallest ATP challenger or ITF events each week using
get_atp_lower_level_tournaments. - Construct a full-season ATP tournament timeline with surface type and prize money from
get_atp_season_calendar. - Retrieve the current ATP top-50 with points and country data for ranking comparison tools.
- Map player slugs from
get_atp_rankingsto full profiles to build a searchable player database.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does TennisExplorer have an official developer API?+
What does get_atp_season_calendar return, and how does the level filter work?+
start_date ascending. Each record includes name, url, level (main or lower), surface, start_date in ISO YYYY-MM-DD format, and prize_money as a display string (e.g. '$6,650,000') or null when not published. The optional level parameter accepts main, lower, or all; omitting it returns all tournaments.Does the API cover WTA rankings or a WTA season calendar?+
get_weekly_tournaments (which includes wta_main and wta_lower arrays) and through get_today_matches filtered by wta-single or wta-double. Dedicated WTA rankings and a full WTA season calendar are not included. You can fork this API on Parse and revise it to add those endpoints.Are historical match results or head-to-head records available?+
get_player_profile returns a recent_matches array with recent or upcoming matches (tournament, round, date), but there is no endpoint for historical match archives or head-to-head records between two players. You can fork this API on Parse and revise it to add the missing endpoint.What is the freshness of rankings and match data?+
get_atp_rankings and matches from get_today_matches are based on the live state of the source site. There is no built-in timestamp in the response; treat results as current at the time of the request rather than as a point-in-time historical snapshot.