TennisExplorer Scraper - Results, Odds, Fixtures & Rankings
Pricing
from $0.83 / 1,000 matches
TennisExplorer Scraper - Results, Odds, Fixtures & Rankings
Scrape TennisExplorer: ATP and WTA match results by date with set scores, tiebreaks, winners and bookmaker odds; upcoming matches with head-to-head counts and odds; ATP and WTA rankings with points and movement. Any date, any tour. No login, no browser. JSON, CSV, Excel.
Pricing
from $0.83 / 1,000 matches
Rating
0.0
(0)
Developer
Scrape Sage
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Scrape tennis match results, upcoming fixtures and rankings from TennisExplorer.com - the site tennis bettors and analysts use for day-by-day ATP and WTA data. Pick a date range and get every finished match with set-by-set scores, tiebreak points, the winner and the bookmaker odds the match closed at; pick upcoming days and get the schedule with head-to-head counts and pre-match odds; or pull the current ATP or WTA ranking table with points and weekly movement. No login, no API key, no browser - JSON, CSV or Excel.
Why this actor exists (demand): the TennisExplorer niche on Apify draws ~180 monthly users, almost all on one results-only actor with no reviews. This one covers results, fixtures and rankings, keeps the odds and tiebreaks the site shows, and adds implied probabilities - the inputs a betting model or a tennis-stats project actually needs.
Modes
| Mode | What you get | Record |
|---|---|---|
| results | Finished matches for each day in the range: tournament (with country and tour), players (with seeds and profile URLs), sets won, per-set games with tiebreak points, winner, closing odds for both players, implied probabilities, match-detail URL | match (status: finished) |
| upcoming | Scheduled matches for each day: time, tournament, players, head-to-head counts, pre-match odds and implied probabilities, match-detail URL | match (status: upcoming) |
| rankings | The current ATP or WTA ranking table: rank, weekly movement, player, country, points, ranking date, profile URL | ranking |
Tour filter for results / upcoming: ATP + WTA singles, ATP singles only, or WTA singles only.
Input
Results for a week of the US Open, both tours:
{ "mode": "results", "tour": "all", "dateFrom": "2026-08-25", "dateTo": "2026-08-31", "maxResults": 2000 }
Tomorrow's WTA schedule with odds and H2H:
{ "mode": "upcoming", "tour": "wta-single", "dateFrom": "2026-09-03" }
Top 200 ATP ranking:
{ "mode": "rankings", "rankingTour": "atp", "maxResults": 200 }
- Date from / Date to -
YYYY-MM-DD, inclusive, up to 60 days per run. Results default to yesterday, upcoming to today. - Max records - caps matches or ranking rows across the run.
Leave everything empty and the run returns a small free sample (yesterday's results, all tours, up to 100 matches).
Example output (match)
{"type": "match","status": "finished","date": "2026-08-31","time": "23:45","tournament": "US Open","tournamentUrl": "https://www.tennisexplorer.com/us-open/2026/atp-men/","tournamentCountry": "US","tour": "ATP","player1": "Khachanov K.","player1Url": "https://www.tennisexplorer.com/player/khachanov/","player1Seed": null,"player2": "Burruchaga R.","player2Url": "https://www.tennisexplorer.com/player/burruchaga/","setsPlayer1": 3,"setsPlayer2": 0,"score": "6-3 6-0 6-1","sets": [{ "set": 1, "player1": 6, "player2": 3, "tiebreak": null }, { "set": 2, "player1": 6, "player2": 0, "tiebreak": null }, { "set": 3, "player1": 6, "player2": 1, "tiebreak": null }],"winner": "Khachanov K.","oddsPlayer1": 1.25,"oddsPlayer2": 3.98,"impliedProbPlayer1": 80,"impliedProbPlayer2": 25.13,"matchId": "3307389","matchUrl": "https://www.tennisexplorer.com/match-detail/?id=3307389","scrapedAt": "2026-09-02T06:00:00.000Z"}
ranking records: rank, move, player, playerUrl, country, points, tour, rankingDate.
Match details (opt-in)
Turn on Add match details (results / upcoming) to open each match's detail page and enrich the record with:
- Head-to-head - the career H2H record (
h2hPlayer1Wins/h2hPlayer2Wins) plush2hMeetings[]: every prior meeting with year, tournament, surface, round, score and winner. - Player comparison -
player1Detail/player2Detail: singles ranking, birthdate, height, weight and playing hand. - All bookmaker odds -
oddsBookmakers[](up to 30 books with each player's price),bestOddsPlayer1/2andavgOddsPlayer1/2across the market,oddsBookmakerCount, andoddsMarketCounts(how many Home-Away, Over-Under, Asian-Handicap and Correct-Score lines the match has). The listing-leveloddsPlayer1/2remain the single closing price.
One extra request per match, so cap it with Max match details (default 200). TennisExplorer does not publish per-point serve statistics (aces, first-serve %), so those are not available from any lane.
Use cases
- Betting models - closing odds and implied probabilities alongside the actual result, day by day, for both tours.
- Tennis analytics - set scores with tiebreak points for surface, form and momentum studies; ranking movement over time when scheduled weekly.
- Fixture feeds - tomorrow's schedule with H2H and odds for previews, newsletters and apps.
- Player tracking - filter the dataset by
player1/player2or profile URL to follow specific players through a tournament.
Notes and limits
- Doubles are not included (TennisExplorer lays doubles out differently); Challenger, ITF and qualifying singles that TennisExplorer lists on the day pages are included.
- Odds are the two decimal prices TennisExplorer shows per match (home / away); a missing odd is an honest
null. - Match statistics (aces, serve percentages) live on each match-detail page and are not part of this version.
Use with AI assistants (MCP)
This actor is available through the Apify MCP server, so assistants like Claude can call it as a tool - "give me yesterday's WTA results with the odds" - and get structured data back.
Agent-ready: autonomous payments (x402 & Skyfire)
This actor is agent-ready - AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:
- x402 - an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server - no account, no API key.
- Skyfire - agent-to-service payments for fully autonomous AI-agent workflows.
Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.
Pricing
Pay-per-event, tiered by volume: match records from $0.0015 (down to $0.00083 on the Gold tier and above) and ranking rows from $0.001 (down to $0.00055). You pay only for records actually returned; days with no matches and blocked requests cost nothing.
Every run finishes with a clear status message; empty runs never crash and never bill.
TennisExplorer is a trademark of its owner. This actor is an independent tool that reads publicly available pages and is not affiliated with or endorsed by TennisExplorer.