TennisExplorer Scraper — ATP/WTA Results, Rankings, Players
Pricing
Pay per event
TennisExplorer Scraper — ATP/WTA Results, Rankings, Players
Extract ATP, WTA, Challenger and ITF match results, upcoming schedules, player profiles and rankings from TennisExplorer, with derived match status and a pinned UTC day boundary.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Oswaldo Carabano
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
TennisExplorer Results, Schedule, Players & Rankings Scraper
Extract ATP, WTA, Challenger and ITF tennis data from TennisExplorer: finished match results with set-by-set scores, upcoming schedules, player profiles with career history, and ranking tables going back to 1995.
🚧 Pre-release. Not published yet.
What makes this one different
1. Match status you can actually filter on. TennisExplorer does not label
retirements or walkovers anywhere — an unfinished match just shows a scoreline that
never closes. This Actor derives a status field (completed, retired,
walkover) and it works for best-of-3 and best-of-5 alike, without needing to know
which is which. Validated against 2,364 matches across nine tournaments with
different formats, including Davis Cup, which mixes both on the same page.
About 4.6 % of matches are affected.
retired means exactly the match started and did not finish — retirement, injury,
default, or an abandoned dead rubber. The source does not distinguish them, so
neither do we.
2. A day boundary that does not move. The site decides which matches belong to
which day from a timezone cookie. The same date returned 227 matches in one
timezone and 269 in another during testing. Every request here is pinned to
UTC, so two runs of the same date return the same set of matches. Every time
field is UTC and named start_time_utc.
3. Full names in doubles. The site truncates the visible team name ("Roger-Vas"). This Actor reads the full name from the underlying attribute. That is 17.4 % of all rows.
4. History back to 1995. The same input works for any past date. A full season is around 148,000 matches — that is measured, not estimated.
Output
One entity type per run, so the file you download has one clean shape:
entityType | Rows | Typical size |
|---|---|---|
results | Finished matches for a date range | 150–600 per day |
schedule | Upcoming and in-progress matches | ~200 per day |
players | Profiles, optionally with match history | 1 per player |
rankings | ATP or WTA tables, singles / doubles / race | 50 per page |
A single day of results costs one request. A full season is 365.
Pricing
Two tiers, so bulk history is actually affordable:
- $0.0015 per result for the first 10,000 rows of a run
- $0.0003 per result after that
- $0.0024 surcharge per match when
includeMatchDetailis on - Free to start a run
- Failed requests are never charged. They go to the
ERRORSrecord instead.
A week of results is about $4. A full season of ~148,000 matches is about $56.
Betting odds are off by default
includeOdds is off on purpose. The odds on this site come from bookmakers, not from
the site itself, and redistributing them sits in a very different position from match
scores. Turn it on only if you have your own basis for using them.
Data notes
- All times and dates are UTC.
- Players under 18 are returned with
birth_yearinstead of a fullbirthdate, and without a photo URL. - For a match that did not finish, the site's result column is a won/lost flag,
not a set count — it reads
1-0no matter how many sets were played.home_setsandaway_setsare recounted from the scoreline in that case, so they are never the flag.setsalways carries the raw scoreline. maxConcurrencyis capped to what fits in the memory the run was given. Give a backfill 1024 MB or more if you want it to go fast.
Not affiliated
This Actor is an independent tool. It is not affiliated with, endorsed by, or connected to TennisExplorer or its operator.
Privacy requests: privacy@actorstack.dev