# TennisExplorer Scraper ($5.49/1K): Tennis Results & Odds (`tsutseisoftware/tennisexplorer-scraper`) Actor

Scrape TennisExplorer: ATP, WTA, Challenger and ITF results back to 1990, fixtures with bookmaker odds and odds history, value bets, match statistics and point by point, H2H, players, rankings, tournament calendars and Elo; filters, monitoring and alerts. Unofficial.

- **URL**: https://apify.com/tsutseisoftware/tennisexplorer-scraper.md
- **Developed by:** [Tsutsei Software](https://apify.com/tsutseisoftware) (community)
- **Categories:** Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.95 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## TennisExplorer Scraper: Tennis Results, Odds, H2H & Rankings

Scrape [TennisExplorer](https://www.tennisexplorer.com) tennis data: the results of any day back to 1990, today's matches and the schedule with the bookmakers' odds, tournament seasons with rounds, players with their matches and profiles, ATP and WTA rankings of any week, and the head-to-head of two players. ATP, WTA, Challenger, ITF and UTR, singles and doubles, with sets and tiebreaks, retirements and walkovers, tournament level, surface and prize money. Options add the match details (players' bio, head-to-head before the match, the odds of every bookmaker with the opening odds and their movement, over/under, handicap and correct-score markets, every line graded after the match), the odds of the bookmakers of your country from Flashscore (also on the 1st and 2nd set, odd/even games and in-play), value bets and surebets against Pinnacle, match statistics and point by point with break, set and match points for every tour, the live state of matches in progress, each player's rank and points in the week of the match, fatigue, Elo ratings with the win probability, prediction markets, live rankings, the doubles Race, the betting ranking, files in the Sackmann and tennis-data.co.uk layouts, monitoring and alerts.

This is an unofficial tool. It is not affiliated with, endorsed by or connected to TennisExplorer or Livesport.

### Why use this TennisExplorer scraper?

- **Every way in, one actor:** days or a date range (up to 366 days per run, back to 1990), tournament seasons by name or URL, players by name or URL (one season, several, or the whole career), match URLs or IDs, rankings of any week since 1998, head-to-head pairs like "Sinner vs Alcaraz".
- **Ready for betting models and backtests:** average odds of every match, implied probabilities without the margin, the favourite and an upset flag; with details the odds of every bookmaker with the opening odds, their time and every move, best odds and the move from opening to closing in %.
- **No look-ahead:** the head-to-head of a match lists only the meetings before it, and the rank at the time of the match comes from the official ranking of that week (today's rank is a separate field).
- **Clean tennis data:** sets and tiebreaks as numbers, retirements and walkovers recognised, rounds, seeds, qualification flag, tournament level (Grand Slam, tour finals, ATP/WTA tour, Challenger, ITF, UTR, team events, exhibitions), surface and prize money on every match.
- **Statistics and point by point for every match:** aces, double faults, serve and return, break points, winners and unforced errors for the match and per set, and every game with its points, for ATP, WTA, Challenger and ITF, singles and doubles (from Flashscore; WTA singles from the WTA with the duration). Live matches get the server and the points of the game.
- **Backtests without spreadsheets:** every odds line of a finished match is graded (won, lost, push, void), with games won, the games difference, best of 3 or 5, rest days and the ranking points at the time of the match.
- **Value bets and surebets:** every odds line gets its fair price (Pinnacle without margin, else the bookmakers' consensus), its edge in % and whether it is the best price; each match gets its best edge, the number of value bets and the margin of the best prices of both players (below 0 = a surebet). "Min edge (%)" keeps only matches with a value bet, for alerts.
- **The bookmakers of your country:** with "Add Flashscore odds" about 20 bookmakers of the UK (bet365, Betfred, Paddy Power, Sky Bet, William Hill...) or of another of 56 countries, on the match, the 1st and the 2nd set, odd or even games, and the in-play prices of a match in progress.
- **Model inputs ready:** win probability from both players' Elo (overall, surface, average) and its edge against the bookmakers, fatigue (matches and sets in the last 7 and 14 days, a retirement in the previous match), dominance ratio, and the finished matches as CSV in the Sackmann and tennis-data.co.uk column layouts.
- **Live rankings and the doubles Race:** the ATP and WTA ranking as it stands during the week (points won this week, current tournament, points with the next round), the doubles Race of both tours, and series of weekly rankings with a rank range, only the players who moved, several countries.
- **Betting ranking:** TennisExplorer's ranking of the most profitable (or loss-making) players to bet on, by season, last month or the last two weeks.
- **Monitoring and alerts:** scheduled runs return only new matches, results and odds moves above your threshold, and matches gone from the lists, with notifications to Telegram, Slack, Discord, WhatsApp or a webhook.

| | This actor | Typical TennisExplorer scraper |
|---|---|---|
| Sources | **days and ranges, tournaments, players (all seasons), match IDs, rankings of any week, head-to-head pairs** | one day, or days only |
| Match details | **bio, age at the match, H2H before the match, every bookmaker in 4 markets, opening odds and history** | some, often a separate price |
| Rank at the time of the match | **yes** (weekly ranking archive, with points) | today's rank |
| Statistics and point by point | **every tour, singles and doubles, per set** | none, or one tour |
| Odds lines graded after the match | **yes** (won, lost, push, void) | rarely |
| Bookmakers of your country, set markets, in-play | **yes** (Flashscore, 56 countries) | no |
| Value bets and surebets against Pinnacle | **yes** (every line, every match) | no |
| Betting ranking, Elo ratings with win probability | **yes** | no |
| Live rankings, doubles Race, ranking series | **yes** | no |
| Level, surface and prize money on every match | **yes** | some |
| Player profiles with career and season records by surface, titles and a summary of the matches read | **yes** | rarely |
| Monitoring of results and odds moves, alerts | **yes** (Telegram, Slack, Discord, WhatsApp, webhook) | rarely |

### What data can you get?

| Field | Example |
|---|---|
| Match | id 3377747, url, tournament "Masters Cup ATP", tournamentId, season 2026, tour atp, gender men, draw singles |
| Tournament | level tour-finals (grand-slam, main, team, challenger, itf, utr, lower, exhibition), surface indoors (hard, clay, grass), prizeMoney 15 750 000, prizeCurrency USD, tournamentCountry |
| Round | round SF, roundName semifinal, isQualification (tournament, player and match pages) |
| Time | startTime 2026-11-16T20:00:00Z, startTimeLocal (your time zone), matchDate, timeKnown |
| Status | status finished (scheduled, retired, walkover, live, cancelled), resultType completed, retired or walkover, bestOf 3 or 5 |
| Players | homePlayer "Medvedev D.", awayPlayer, IDs, profile URLs, seeds; doubles: the pairs |
| Score | homeScore 2, awayScore 0 (sets), homeSetScores \[7, 6], awaySetScores \[6, 3], tiebreak points, scoreText "7-6(4), 6-3", setsPlayed, totalGames, winner, winnerName, loserName |
| Odds | oddsHome 1.26, oddsAway 3.85 (average of the bookmakers), probabilityHome 75.3 %, oddsMarginPercent 5.34, favorite, upset; also as fractional or American text |
| Rank at the match (option) | homeRankAtMatch 5, awayRankAtMatch 7, homeRankPoints, awayRankPoints, rankDate 2026-11-09 |
| Games | homeGamesWon 13, awayGamesWon 9, gamesDifference 4 |
| Match details (option) | full names, birth date, age at the match, height, weight, handedness, current rank, head-to-head before the match (wins and the meetings with year, tournament, surface, round and score), average, best and opening odds (and the best opening odds), odds move in %, bookmakers, every bookmaker's line of the match winner, over/under (sets and games), Asian handicap and correct score, with the opening odds and time, the outcome of the line after the match (won, lost, push, void) and, with "Add odds history", every move |
| Player profiles | rowType player: country, height, weight, age, birth date, handedness, current and highest rank (singles, doubles), career wins and losses by surface, wins and losses by season, titles with level, surface and prize money, next match, and from the matches read: win rate, tiebreaks and deciding sets won and lost, recent tournaments (dates, matches, wins, last round) |
| Rankings | rowType ranking: ranking atp-singles, rankingDate, rank, rankChange, player, country, points |
| Head-to-head | rowType h2h: balance, both players' bio, every meeting |
| Tournament category | category grand-slam, tour-finals, 1000, 500, 250 or 125 of the tournament in its season (from the winner's ranking points; ATP and WTA since 2009) |
| Head-to-head by surface | wins of each player on hard, clay, grass and indoors, and the last meeting (year, tournament, surface, round, winner, score), in match details and head-to-head rows |
| Recent form (option) | each player's last N matches before the match (opponent, result, score, odds), the form "WWLWL", the date of the previous match and the rest days |
| More match facts (options) | rounds for the matches of days, the players' countries, both players' wins and losses by season and surface, turned pro, opening probabilities |
| Match statistics (option) | aces, double faults, first serve in and won, second serve won, break points won, saved and faced, service and return points, service games, winners, unforced errors, net points, total points, for the match and per set, and the full list of the source; the duration of the match and of each set and the umpire (every tour, singles and doubles, finished and live matches) |
| Point by point (option) | every game: set, games after it, server, break, the points with break, set and match points marked ("15:0, 30:0, 40:0 (set point)"), every score with isBreakPoint, isSetPoint, isMatchPoint, their counts per game, tie-breaks with their points |
| Flashscore odds (option) | oddsLines with source flashscore: the bookmakers of "Odds country" (GB, US, DE... 56 countries), markets winner, over/under, handicap, correct score and odd/even, periods match, set1, set2, opening odds; oddsLive for in-play prices |
| Value bets | on every odds line fairOdds, fairSource (pinnacle or consensus), edgePercent, isBestPrice, isValueBet; on the match bestEdgePercent, valueBetCount, surebetMarginPercent, surebetCount |
| Elo win probability (with Elo) | homeEloWinProbability 64.3, awayEloWinProbability, homeSurfaceEloWinProbability, homeEloWinProbabilityBlended, eloHomeEdge against the bookmakers |
| Fatigue (with recent form) | homeMatchesLast7Days, homeMatchesLast14Days, homeSetsLast7Days, homeSetsLast14Days, homeRetiredLastMatch (and away) |
| Dominance ratio (with statistics) | homeDominanceRatio 1.42, awayDominanceRatio |
| Live rankings | rowType ranking atp-live or wta-live: rank, rankChange against the official ranking, player, age, country, points, pointsChange this week, currentTournament, nextRoundPoints, maxPoints, careerHighRank (top 1,000) |
| Doubles Race | rowType ranking atp-doubles-race or wta-doubles-race: rank, previousRank, rankChange, the pair, playerIds, playerUrls, countries, points, tournamentsPlayed |
| Match files for models | MATCHES-SACKMANN.csv (tourney\_*, winner\_*, loser\_\*, score, w_ace ... l_bpFaced, ranks) and MATCHES-TENNIS-DATA.csv (W1 ... L5, WRank, B365W, PSW, MaxW, AvgW) of the finished matches |
| Live state (option) | matches in progress: set, server, games of the set, points of the current game |
| Elo (option) | each player's current Elo overall and on the match's surface (Tennis Abstract, weekly); Elo ranking rows with hard, clay and grass Elo and the peak |
| Betting ranking | rowType ranking: rank, player, profit or loss, matches, as favourite and outsider, by season, month or two weeks |
| Search players | rowType search: every player a name finds, the most relevant first, the one used marked as chosen |
| Prediction markets (option) | Kalshi and Polymarket prices of each player (probability), bid and ask, volume, Polymarket set and total markets, their average and the edge against the bookmakers |
| ESPN (option) | ESPN match and player IDs, court and venue (Grand Slams, ATP and WTA tour) |
| Tournament calendars | rowType tournament: start date, tour, level, category, surface, prize money and currency, draw sizes, singles winner |
| Rankings | singles, doubles and Race of ATP and WTA, any week since 1998 or every week of a period, by one or more countries, a rank range (Min rank to Max rank), only the players who moved, in the order you choose, with the players' profiles if you want |
| Player's view | rows of a player's pages: result for the player, opponent, the player's and the opponent's odds |
| Injuries (option, personal data) | the injuries and retirements a player's page lists (dates, tournament, reason) |
| Monitoring | changeType new, updated or expired, changedFields, previous status, score and odds, odds move in % and an alert text |

Extra export formats: a printable HTML report or a Markdown table, besides Excel, CSV and JSON. **Output fields** keeps only the fields you list.

### How to scrape TennisExplorer

1. Choose the **days** (e.g. yesterday, or 2025-01-01 to 2025-12-31) and the **match types** (men's or women's singles or doubles), or add **TennisExplorer URLs**, **players**, **tournaments**, **rankings** or **head-to-head pairs**.
2. Add filters if you want (tournament level, surface, status, tournaments, players, rounds, no qualification, only with odds).
3. Turn on **Add match details** or **Add rank at the time of the match** if you need them.
4. Run it, or schedule it in monitoring mode. Download the data as Excel, CSV or JSON, or connect it to your tools.

### Use cases

#### Yesterday's results of the ATP and WTA tour with odds

```json
{
  "dateFrom": "yesterday",
  "matchTypes": ["atp-single", "wta-single"],
  "levels": ["grand-slam", "tour-finals", "main"],
  "maxItems": 500
}
```

#### A season of results for a betting model, with the rank at the time of each match

```json
{
  "dateFrom": "2025-01-01",
  "dateTo": "2025-12-31",
  "matchTypes": ["atp-single"],
  "levels": ["grand-slam", "tour-finals", "main"],
  "excludeQualification": true,
  "includeRankAtMatchTime": true,
  "maxItems": 0
}
```

#### Tomorrow's matches with the odds of every bookmaker and the head-to-head

```json
{
  "dateFrom": "tomorrow",
  "matchTypes": ["atp-single", "wta-single"],
  "levels": ["grand-slam", "main"],
  "includeMatchDetails": true,
  "oddsMarkets": ["winner", "overUnder", "handicap"],
  "includeOddsHistory": true,
  "maxItems": 200
}
```

#### A player's whole career, with the profile

```json
{
  "players": ["Jannik Sinner"],
  "playerSeasons": ["all"],
  "includePlayerProfile": true,
  "maxItems": 0
}
```

#### Ten years of Wimbledon, men and women

```json
{
  "tournaments": ["Wimbledon"],
  "tournamentSeasons": ["2016", "2017", "2018", "2019", "2021", "2022", "2023", "2024", "2025", "2026"],
  "matchTypes": ["atp-single", "wta-single"],
  "maxItems": 0
}
```

#### Odds moves only, with alerts

```json
{
  "upcomingDays": 1,
  "matchTypes": ["atp-single", "wta-single"],
  "levels": ["grand-slam", "tour-finals", "main"],
  "onlyNewOrChanged": true,
  "monitoringKey": "odds-moves",
  "monitorOdds": true,
  "onlyOddsAlerts": true,
  "minOddsChangePercent": 5
}
```

#### Bookmakers against prediction markets

```json
{
  "upcomingDays": 2,
  "matchTypes": ["atp-single", "wta-single"],
  "categories": ["grand-slam", "1000", "500"],
  "includeMatchDetails": true,
  "includePredictionMarkets": true,
  "maxItems": 100
}
```

#### The 1000 tournaments of a season, and the doubles ranking

```json
{
  "calendars": ["atp", "wta"],
  "calendarYears": ["2025"],
  "categories": ["1000"],
  "rankings": ["atp-doubles", "wta-race"],
  "maxRank": 50,
  "maxItems": 0
}
```

#### Statistics and point by point of yesterday's matches, all tours

```json
{
  "dateFrom": "yesterday",
  "matchTypes": ["atp-single", "wta-single"],
  "levels": ["grand-slam", "tour-finals", "main", "challenger"],
  "includeMatchStatistics": true,
  "includePointByPoint": true,
  "maxItems": 200
}
```

#### A backtest: graded odds lines, rest days and ranking points

```json
{
  "lastDays": 30,
  "matchTypes": ["atp-single"],
  "categories": ["1000", "500", "250"],
  "includeMatchDetails": true,
  "oddsMarkets": ["winner", "overUnder", "handicap"],
  "recentFormMatches": 5,
  "includeRankAtMatchTime": true,
  "maxItems": 0
}
```

#### Value bets against Pinnacle, with the bookmakers of the UK

```json
{
  "upcomingDays": 1,
  "matchTypes": ["atp-single", "wta-single"],
  "levels": ["grand-slam", "tour-finals", "main", "challenger"],
  "includeMatchDetails": true,
  "includeFlashscoreOdds": true,
  "oddsCountry": "GB",
  "oddsMarkets": ["winner", "overUnder", "handicap"],
  "oddsScopes": ["FULL_TIME", "FIRST_SET"],
  "minEdgePercent": 3,
  "includeElo": true,
  "maxItems": 100
}
```

Matches without a line 3% above its fair price are not saved or charged; the odds pages read to rate them are charged as "Extra page".

#### A season in the Sackmann and tennis-data.co.uk layouts

```json
{
  "lastDays": 90,
  "matchTypes": ["atp-single"],
  "levels": ["grand-slam", "tour-finals", "main"],
  "includeMatchDetails": true,
  "includeMatchStatistics": true,
  "includeRankAtMatchTime": true,
  "csvExports": ["sackmann", "tennis-data"],
  "maxItems": 0
}
```

#### Live rankings, the doubles Race and the top 100 of every week of a season

```json
{
  "rankings": ["atp-live", "wta-live", "atp-doubles-race", "atp-singles"],
  "rankingDate": "2025-01-01",
  "rankingDateTo": "2025-12-31",
  "maxRank": 100
}
```

#### Live matches with the server and the points

```json
{
  "dateFrom": "today",
  "matchTypes": ["atp-single", "wta-single"],
  "statuses": ["live"],
  "includeLiveState": true,
  "includeMatchStatistics": true
}
```

#### The betting ranking and Elo ratings

```json
{
  "bettingRankings": ["season", "month"],
  "rankings": ["atp-elo", "wta-elo"],
  "maxRank": 100
}
```

#### Which "Nadal"? Search first

```json
{
  "searchPlayers": ["Nadal", "Murray"],
  "maxRank": 10
}
```

#### Rankings and head-to-heads

```json
{
  "rankings": ["atp-singles", "wta-singles"],
  "rankingDate": "2024-01-01",
  "maxRank": 200,
  "h2hPairs": ["Sinner vs Alcaraz", "Sabalenka vs Swiatek"]
}
```

#### Results and odds moves of the day, every 15 minutes, with alerts

```json
{
  "dateFrom": "today",
  "matchTypes": ["atp-single", "wta-single"],
  "levels": ["grand-slam", "tour-finals", "main"],
  "onlyNewOrChanged": true,
  "monitoringKey": "tour-today",
  "monitorOdds": true,
  "minOddsChangePercent": 5,
  "telegramBotToken": "<your bot token>",
  "telegramChatId": "<your chat ID>"
}
```

#### Monitoring mode explained

With **Monitoring: only new or changed matches**, every run remembers what it saw (under your **Monitoring key**) and returns only new matches and matches whose status, score or start time changed (and, with **Monitoring: odds changes**, whose average odds moved at least your threshold). "Max results" then means the first N matches in the website's order are watched. Unchanged matches are not returned and not charged; every list read is charged as "Monitoring page". Rankings, profiles and head-to-heads are returned when the rank, points or record change.

#### Notifications

Add a Telegram bot, a Slack or Discord webhook, WhatsApp or any webhook URL: after each run you get one message with the saved matches (players, score, tournament, status and odds, and what changed). With "Notify only when something was found" a run without results sends nothing.

#### Run summary (SUMMARY)

Every run saves a free SUMMARY record: rows saved by type and status, which player or tournament each name was matched to, rows read and saved per source, and how many matches each filter left out.

With **Monitoring: matches gone from the lists**, a scheduled or live match that was on a list read in full last time and is not there any more (cancelled, withdrawn, moved) is returned once with changeType `expired`.

### How much does it cost to scrape TennisExplorer?

Pay per result: you pay for the rows saved, plus the add-ons you turn on, only for the matches they are found for. Filtered-out matches, and matches without statistics, odds or markets, are not charged for them.

| Event | Price |
|---|---|
| Result (a saved row) | $5.49 per 1,000 (Bronze $5.25, Silver $4.59, Gold $3.95) |
| Match details | $0.50 per 1,000 matches |
| Match statistics (with point by point) | $0.50 per 1,000 matches |
| Flashscore odds | $0.50 per 1,000 matches |
| Prediction markets | $0.50 per 1,000 matches |
| Extra page, monitoring page | $0.20 per 1,000 pages |
| Notification | $0.001 per run that sent it |
| Run start | $0.003 |

No extra platform costs: compute and traffic are included in these prices.

The Pricing tab has the current prices. The live state, Elo ratings with the win probability, value bets, fatigue, graded odds lines, games, rest days and the match files are free. Pages read beyond what the saved rows explain (for example a whole year of days with a narrow filter) are charged as "Extra page".

### Input example

```json
{
  "dateFrom": "yesterday",
  "matchTypes": ["atp-single"],
  "maxItems": 20
}
```

### Output example

```json
{
  "id": "3377747",
  "rowType": "match",
  "source": "tennisexplorer",
  "url": "https://www.tennisexplorer.com/match-detail/?id=3377747",
  "tournament": "Masters Cup ATP",
  "tournamentId": "masters-cup-atp",
  "season": 2026,
  "tour": "atp",
  "gender": "men",
  "draw": "singles",
  "level": "tour-finals",
  "surface": "indoors",
  "prizeMoney": 15750000,
  "prizeCurrency": "USD",
  "startTime": "2026-11-16T20:00:00Z",
  "matchDate": "2026-11-16",
  "status": "finished",
  "resultType": "completed",
  "homePlayer": "Medvedev D.",
  "awayPlayer": "Cobolli F.",
  "homePlayerId": "medvedev-e0d2d",
  "awayPlayerId": "cobolli-d6311",
  "homeScore": 2,
  "awayScore": 0,
  "homeSetScores": [7, 6],
  "awaySetScores": [6, 3],
  "scoreText": "7-6(4), 6-3",
  "totalGames": 22,
  "winner": "home",
  "winnerName": "Medvedev D.",
  "oddsHome": 1.26,
  "oddsAway": 3.85,
  "probabilityHome": 75.3,
  "probabilityAway": 24.7,
  "oddsMarginPercent": 5.34,
  "favorite": "home",
  "upset": false,
  "homeRankAtMatch": 5,
  "awayRankAtMatch": 6,
  "detailsIncluded": true,
  "homeFullName": "Medvedev Daniil",
  "homeBirthDate": "1996-02-11",
  "homeAgeAtMatch": 30.76,
  "homeHeightCm": 198,
  "homePlays": "right",
  "h2hHomeWins": 2,
  "h2hAwayWins": 1,
  "oddsHomeOpening": 1.238,
  "oddsHomeBest": 1.3,
  "oddsBookmakers": 15,
  "oddsLines": [{"bookmaker": "10Bet", "source": "tennisexplorer", "market": "winner", "period": "match", "selection": "home", "odds": 1.25, "openingOdds": 1.22, "openingTime": "2026-11-12T17:31:00Z", "fairOdds": 1.268, "fairSource": "pinnacle", "edgePercent": -1.42, "isBestPrice": false, "outcome": "won"}],
  "bestEdgePercent": 2.1,
  "valueBetCount": 2,
  "surebetMarginPercent": 1.3,
  "scrapedAt": "2026-11-18T10:00:00+00:00"
}
```

### Good to know

- **Days and time zones:** TennisExplorer lists matches by Central European days; the actor reads the days that cover your days in your **Time zone** and keeps the matches of your days. Start times are also always in UTC.
- **Unknown times:** older and lower-level matches often have no start time (`timeKnown` false, the time is noon of the day); player pages give only the day.
- **Rounds:** tournament, player and match pages give the round; the lists of days do not, so the "Rounds" filter works with those pages.
- **Dates of tournament pages:** a tournament page writes dates without the year; the actor takes the season's year (a season that began in late December, like the United Cup, keeps its December days in the year before). A match page with its full date always wins.
- **Retirements and walkovers:** the website does not mark them; the actor recognises them from the sets (a walkover has a winner and no sets).
- **Current or then:** `homeCurrentRank` and the profiles are today's values; for the rank in the week of the match use "Add rank at the time of the match". The head-to-head of a match lists only the earlier meetings.
- **Names:** lists give "Surname F.", match pages and profiles the full name. A name you enter is matched to the most relevant player of the website's search (the same surname and first name first, then the website's main player of that name); the log says which, and which others it found. For an exact player paste the URL, or list the candidates with **Search players**.
- **Categories:** the category of a tournament is read from its season (the winner's ranking points on its page): Vienna was a 250 in 2012 and a 500 later. Without points on the page the prize money against the year's 250s decides.
- **Statistics, point by point and live state** come from Flashscore (the same company as TennisExplorer). A match is paired by its start and both surnames: matches of the last and next 7 days directly, older singles through player 1's results. A match the pairing does not find is saved without them and not charged for them; the status says how many.
- **Graded odds lines:** a walkover voids every line; after a retirement only the match winner line counts (the player who goes through), the others are void. The handicap line is player 1's.
- **Max results and profiles:** "Max results" keeps room for the profiles of the players you asked for; if it is smaller than the number of profiles, the status says how many were not saved.
- **Elo:** Tennis Abstract's current ratings (updated weekly, about the top 500 of each tour); a match row gets today's rating (`…EloCurrent`), not the one at the time of an old match.
- **Odds:** the lists give the average of the bookmakers; matches without odds (lower levels, old seasons) have none.
- **Flashscore odds:** a match is paired with Flashscore like the statistics; the odds are those Flashscore shows to visitors of "Odds country" (UK: about 20 bookmakers, most of them not on TennisExplorer). During a match they are the in-play prices at the time of the run (`oddsLive` true). Set lines are in games; handicaps are player 1's.
- **Value bets:** the fair price of a line is Pinnacle's price without its margin where Pinnacle has the same market and line (with "Add match details"), else the average no-margin probability of the bookmakers that price every selection. `edgePercent` = odds x fair probability - 1. Pinnacle is not rated against itself. Long-shot correct scores often show big edges against the consensus: the fair price there is less sure.
- **Fatigue:** counted from the player's matches of the season read for "Recent form" (the 7 and 14 days before the match day); early in January the days of the year before are not counted.
- **Live rankings** come from live-tennis.eu (top 1,000 per tour, during the week); the doubles Race from Flashscore (top 100, then the rest). "Ranking date" and "Ranking country" apply to the TennisExplorer rankings.
- **ITF "Futures":** the men's ITF matches of a day are under one heading "Futures 2026" without a tournament page: they are saved as tournament "Futures 2026", level itf, without surface and prize money.
- **Extra pages:** rounds for the matches of days, players' countries, recent form and ranked players' profiles read one more page per tournament or player; these pages are charged as "Extra page" (see Pricing).
- **Injuries (personal data):** off by default. They are health data of a person; with "Add injuries (personal data)" you are responsible for processing them lawfully (GDPR). They never appear in the log or the notifications.
- **Limitations:** statistics and point by point exist where Flashscore (or the WTA) has them: most tour, Challenger and many ITF matches, fewer of old seasons; older doubles are not paired. The live state and the in-play odds are only for matches in progress at the time of the run. Prediction-market prices of finished matches are the settled prices (no edge then); markets exist mostly for matches of the last weeks and the next days. ESPN covers only the top-level tournaments. Categories before 2009 are null. Elo is only today's rating, for the top ~500 of each tour (not the rating before an old match). Not available: aces and double faults on every point, momentum and UTR rankings (their source refuses automated visitors), Betfair exchange back/lay prices, Tennis Abstract's player splits and charted matches (their data licence does not allow commercial use), entry status Q/WC/LL (TennisExplorer does not show it).

### For AI agents and API users

Call the actor with the input JSON above (Apify API, MCP or the Apify client). Each row has `rowType` (`match`, `player`, `ranking`, `h2h`, `tournament`, `search`), a stable `id` and `url` (ranking rows: the player's profile). Betting ranking, Elo, live ranking and doubles Race rows are `ranking` rows (`ranking` `betting-best-season`, `atp-elo`, `atp-live`, `atp-doubles-race`...). Matches link to players by `homePlayerId` and `awayPlayerId`, the same IDs as in profiles and rankings. The SUMMARY record of the run's key-value store says what was read and what the filters left out.

### Troubleshooting

- **"Nothing to read":** give days with match types, or URLs, players, tournaments, rankings or head-to-head pairs.
- **"Not available from the country of this connection":** TennisExplorer blocks visitors from the Czech Republic; with your own proxy use another country.
- **A player or tournament not found:** check the spelling (Roland Garros is "French Open"), or paste its TennisExplorer URL.
- **No match passed the filters:** check the tournament name as TennisExplorer writes it ("Helsinki challenger"), or the level.

### Integrations

Connect the results to the tools you already use with the built-in integrations of Apify (the **Integrations** tab of the actor or of a saved task), with no code:

- **Google Sheets or Google Drive:** the results of every run in a spreadsheet or a file.
- **Zapier, Make and n8n:** start a workflow when a run finishes, or start the actor from one.
- **Slack or e-mail:** a message from Apify when a run finishes or fails.
- **Webhooks:** your own address gets the details of each run.
- **API and MCP:** run the actor from your code, or let an AI assistant run it through the Apify MCP server.

The results also download as Excel, CSV, JSON or XML from the **Output** tab.

### Privacy and error reports

When a run fails, the actor sends its developer a short error report: the error, the run ID and your input with secrets left out (tokens, webhooks, e-mails and similar values are hidden). Your results are never sent. Reports are deleted after at most 120 hours (5 days). To send nothing, turn off **Send error reports** (`sendErrorReports: false`). Questions about your data: open an issue in the **Issues** tab of this actor.

### WhatsApp notifications: setup

The actor sends the message from your own WhatsApp business number through the WhatsApp Cloud API of your Meta business account. You need a Meta business account; the actor uses only the values you enter in the **Notifications** section (the token and the numbers are stored encrypted and never written to the log).

1. **Create an app.** In Meta for Developers open **My Apps → Create app** and choose the use case **Connect with customers through WhatsApp**.
2. **Get a sending number.** In the app open **WhatsApp → API Setup**. You can start with the test number Meta gives you and add your own business number there later. Copy the **Phone number ID** (not the number itself) into **WhatsApp phone number ID**.
3. **Confirm the recipients (test number only).** A test number sends only to numbers on its list: in **API Setup**, under **To**, add each recipient's number and confirm it with the code WhatsApp sends to it.
4. **Create a permanent access token.** The token shown in API Setup expires within hours. In **Business settings → System users** add a system user, use **Assign assets** to give it your app (and your WhatsApp account), then **Generate token** for the app with the permissions `whatsapp_business_messaging` and `whatsapp_business_management` and the expiry you want. Paste it into **WhatsApp access token**.
5. **Create a message template (recommended).** In **WhatsApp Manager → Message templates → Create template** choose the category **Utility**, a name (e.g. `apify_results`) and a language, and write a body with two variables, for example: `New results of your Apify task: {{1}} Open the dataset: {{2}} (sent automatically after each run).` Meta does not accept a body that starts or ends with a variable and asks for sample values (e.g. `3 new jobs` and a dataset link); keep the text factual, a promotional text is moved to the Marketing category. Approval can take up to 24 hours. Enter the name in **WhatsApp template name** and its language code (e.g. `en_US`, `cs`, `pl`, `de`, as WhatsApp Manager shows it) in **WhatsApp template language**.
6. **Enter the recipients.** **WhatsApp recipient number** takes up to 5 numbers with the country code (e.g. `+420601234567`), separated by commas or new lines. Each number gets its own message.

**What the message contains.** With a template: `{{1}}` is the run summary with the first results on one line (title, company or price, place; never descriptions or contacts) and `{{2}}` the link to the dataset. A template with only `{{1}}` works too, it then gets the link at the end. Without a template the actor sends a text message with one link per result, like in Slack or Telegram.

**Without a template** WhatsApp delivers the message only when the recipient wrote to your business number in the last 24 hours (the customer service window), so a daily or hourly schedule needs a template. The run log says so once per run.

**What it costs.** Meta bills your business account, not this actor: per delivered message, by the message category (a template of the Utility category, or a service message for text in the 24-hour window, with a monthly free allowance per business number) and by the recipient's country. The current rates are in Meta's pricing of the WhatsApp Business Platform. The actor's own notification charge (see the **Pricing** tab) is once per run that delivered its notification, whatever the number of channels and recipients.

**Checked at the start.** When the run starts, the actor checks the token, the phone number ID and, when the token shows its WhatsApp account, the template (name, language, approval), without sending anything. Settings that can't work stop the run with a message that says what to fix, before anything is read from the website.

**When nothing arrives**, the run log names the WhatsApp error and what to do: a template that does not exist in that language or is not approved yet, a template with another number of variables, a recipient missing from the test number's list, an expired token, or the 24-hour window. A failed notification never fails the run and is not charged. Meta can accept a message and still not deliver it later (for example when the recipient's phone is not on WhatsApp); such a run counts as notified.

### More sports data scrapers

Results, statistics and odds from another sports source:

- [Flashscore Scraper](https://apify.com/tsutseisoftware/flashscore-scraper): live scores and results of 29 sports: xG, lineups, statistics, odds, standings, alerts

### FAQ

#### Is it legal to scrape TennisExplorer?

The actor reads public pages that anyone can open without logging in, at a moderate pace. It returns sports results and odds and public sports information about professional players (names, country, age, height, rank). Health data (injuries) only with the opt-in **Add injuries (personal data)**, off by default; no contact data. You are responsible for how you use the data, including the terms of the website and the data protection rules (GDPR) that apply to you. If in doubt, ask a lawyer.

#### Do I need a proxy?

No. TennisExplorer is not available from the Czech Republic; the default run works without a proxy.

#### Can I get historical data?

Yes: results of any day back to 1990, tournament seasons back to the 1990s, players' whole careers and weekly rankings back to 1998. Older matches have fewer odds and times.

#### Can I compare bookmakers with prediction markets?

Yes: with "Add prediction markets" every singles match with a Kalshi or Polymarket market gets their prices (= probabilities), the average, and the edge against the bookmakers' probability without margin.

#### Which bookmakers are included?

The bookmakers TennisExplorer shows for the match (often 10Bet, 1xBet, bet365, Betfair, Pinnacle, Unibet and others). Use **Bookmakers** to keep only some.

#### How is it different from other TennisExplorer scrapers?

One actor reads days, ranges, tournaments, players, matches, rankings and head-to-heads, adds the tournament level, category of its season, surface and prize money to every match, gives the odds of every bookmaker with their history and their outcome, statistics and point by point for every tour, the rank and points at the time of the match, keeps the head-to-head free of later meetings, and can monitor results and odds with alerts. The betting ranking and the Elo ratings are in no other TennisExplorer scraper.

This scraper is also known as a TennisExplorer API, tennis results scraper, tennis odds scraper or ATP and WTA data API.

# Actor input Schema

## `dateFrom` (type: `string`):

First day of matches: a date (2025-07-13), or today, yesterday, tomorrow, -7 (7 days ago), +3. Past days give the results (back to 1990), today and later days the schedule with the odds. Empty = no days (use the URLs, players or tournaments below).

## `dateTo` (type: `string`):

Last day (same formats). Empty = only "Date from". At most 366 days per run.

## `lastDays` (type: `integer`):

Instead of the dates: the results of the last N days (yesterday and the N-1 days before; with "Upcoming days" also today). Empty = use the dates.

## `upcomingDays` (type: `integer`):

Instead of the dates: today and the schedule of the next N days, with the odds.

## `matchTypes` (type: `array`):

Which matches of the days, and which tours and draws of the tournaments you name below.

## `maxItems` (type: `integer`):

Maximum rows saved (matches, profiles, ranking rows). 0 = no limit. In monitoring: how many matches are watched (the first N in the website's order).

## `startUrls` (type: `array`):

Tournament seasons (https://www.tennisexplorer.com/wimbledon/2025/atp-men/, with ?type=double for doubles or ?phase=qualification), players (https://www.tennisexplorer.com/player/sinner-8b8e8/, with ?annual=2024 for a season or ?annual=all), matches (/match-detail/?id=3377747), rankings (/ranking/wta-women/?date=2025-07-07), results or schedule pages and head-to-heads (/mutual/a/b/).

## `players` (type: `array`):

Players by name (Jannik Sinner, Swiatek) or URL: their matches of the seasons below, and their profile. The log says which player each name was matched to.

## `tournaments` (type: `array`):

Tournaments by name (Wimbledon, Roland Garros is "French Open", Helsinki challenger) or URL: all matches of the seasons below, with rounds, for the tours and draws chosen in "Match types".

## `matchIds` (type: `array`):

TennisExplorer match IDs (the id= of a match URL, e.g. 3377747).

## `playerSeasons` (type: `array`):

Seasons of the players' matches: years like 2024 and 2025, or "all" for the whole career. Empty = the current season.

## `includePlayerProfile` (type: `boolean`):

One row per player (rowType "player"): country, height, weight, age, handedness, current and highest rank in singles and doubles, career and season wins and losses by surface, titles, the next match, and a summary of the matches read in the run (win rate, tiebreaks and deciding sets won and lost).

## `tournamentSeasons` (type: `array`):

Years of the tournaments (e.g. 2023, 2024, 2025). Empty = the current year.

## `includeQualificationDraws` (type: `boolean`):

For tournaments by name: also read the singles qualification.

## `rankings` (type: `array`):

Also save rankings (rowType "ranking"): rank, move since the week before, player, country, points. Live rankings: the ranking as it stands during the week (live-tennis.eu, top 1,000) with the points won this week, the current tournament and the points at the next round. Doubles Race: the pairs of the season (Flashscore). Elo: Tennis Abstract's current weekly Elo rating overall and on hard, clay and grass, with the peak.

## `rankingDate` (type: `string`):

Ranking of this date (weekly rankings back to 1998; the latest one published on or before it). Empty = the current ranking.

## `rankingDateTo` (type: `string`):

With "Ranking date": every weekly ranking from that date to this one (at most five years per run; each week is charged as its rows). Empty = one ranking.

## `rankingCountry` (type: `string`):

Only the players of these countries, in English as TennisExplorer writes them, separated by commas (e.g. usa, italy, czech-republic, great-britain). Empty = all.

## `rankingSort` (type: `string`):

Order of the ranking rows.

## `includeRankingProfiles` (type: `boolean`):

Also save a player profile row for every ranking row saved (one page per player).

## `maxRank` (type: `integer`):

Ranking rows down to this rank.

## `minRank` (type: `integer`):

Ranking rows from this rank on (e.g. 101 with Max rank 200 = ranks 101 to 200). Empty = from 1.

## `onlyMovers` (type: `boolean`):

Ranking rows only of players whose rank changed since the ranking before.

## `calendars` (type: `array`):

Also save the tournaments of the tour's calendar (rowType "tournament"): start date, level, category, surface, prize money and currency, draw sizes and the winners. The level, surface and category filters apply.

## `calendarYears` (type: `array`):

Years of the calendars (e.g. 2024, 2025). Empty = the current year.

## `calendarSearch` (type: `array`):

Only calendar tournaments whose name has one of these words or names as whole words (e.g. Masters, Open, Halle; "Halle" is not every Challenger).

## `bettingRankings` (type: `array`):

Also save TennisExplorer's betting ranking (rowType "ranking"): how profitable it was to bet on each player in the period (profit or loss of a stake on every match: 100 units as favourite, 50 as outsider), the matches and how often the player was favourite or outsider. Down to "Max rank".

## `bettingRankingType` (type: `string`):

The most profitable or the most loss-making players.

## `bettingRankingYear` (type: `string`):

Season of the betting ranking (e.g. 2025). Empty = the current season.

## `searchPlayers` (type: `array`):

Names to look up (e.g. Nadal): one row per player found (rowType "search": name, ID, URL, country), the most relevant first, with the one "Players" would take marked as chosen. Use it to pick the right player's URL.

## `h2hPairs` (type: `array`):

Two players per line, e.g. "Sinner vs Alcaraz": their balance, bio and every meeting with the tournament, surface, round and score (rowType "h2h").

## `levels` (type: `array`):

Only matches of tournaments of these levels. Empty = all.

## `categories` (type: `array`):

Only matches of tournaments of these official categories of their season (from the winner's ranking points; ATP and WTA since 2009, WTA Premier levels by their present names). Empty = all.

## `surfaces` (type: `array`):

Only matches on these surfaces (as TennisExplorer sorts them: indoor hard courts are "Indoors"). Empty = all.

## `statuses` (type: `array`):

Only matches with these statuses. Empty = all.

## `tournamentFilter` (type: `array`):

Only matches of these tournaments of the days read (names as TennisExplorer writes them, e.g. Wimbledon, Helsinki challenger, or the tournament URL).

## `playerFilter` (type: `array`):

Only matches of these players (a name or surname, e.g. Sinner, Iga Swiatek, or the player ID sinner-8b8e8).

## `rounds` (type: `array`):

Only these rounds, as TennisExplorer writes them: F, SF, QF, R16, 1R, 2R, 3R, Q1... (tournament and player pages give the round; the lists of days do not).

## `draws` (type: `array`):

Only these draws (useful for players' pages, which list singles, doubles and mixed). Empty = all.

## `excludeQualification` (type: `boolean`):

Leave out qualification matches.

## `minOdds` (type: `number`):

Only matches where at least one player's average odds are at least this (decimal, e.g. 1.5).

## `maxOdds` (type: `number`):

Only matches where at least one player's average odds are at most this (e.g. 3.0).

## `onlyWithOdds` (type: `boolean`):

Save only matches that have odds.

## `includeMatchDetails` (type: `boolean`):

Players' full names, birth date, age at the match, height, weight, handedness and current rank, the head-to-head before the match, and the odds of every bookmaker with the average, best and opening odds and how much they moved.

## `includeInjuries` (type: `boolean`):

Player profiles: the injuries and retirements the website lists (dates, tournament, reason such as "retired - left leg"). These are health data of a person: you are responsible for processing them lawfully (GDPR). Off by default.

## `recentFormMatches` (type: `integer`):

With "Add match details": each player's last N finished matches before the match (date, tournament, surface, round, opponent, result, score, odds), the form ("WWLWL"), the rest days and the load: matches and sets in the 7 and 14 days before and a retirement in the previous match. One page per player and season. Empty = none.

## `h2hLimit` (type: `integer`):

How many earlier meetings of the two players to list (only meetings before the match, safe for prediction models).

## `oddsMarkets` (type: `array`):

Markets whose odds of every bookmaker go to "Odds lines" (with "Add match details" or "Add Flashscore odds"). Every line is graded after the match (won, lost, push, void).

## `includeOddsHistory` (type: `boolean`):

With "Add match details": every move of each bookmaker's odds with its time, in "Odds lines".

## `oddsBookmakers` (type: `array`):

With "Add match details": only these bookmakers (e.g. bet365, Pinnacle, 1xBet; case ignored). The average, best and opening odds are then of these. Empty = all.

## `oddsFormat` (type: `string`):

Also give the main odds in this format, as text next to the decimal numbers (oddsHomeText, oddsAwayText).

## `includeFlashscoreOdds` (type: `boolean`):

The odds of the bookmakers Flashscore shows in the country below (GB: about 20, such as bet365, Betfred, Paddy Power, Sky Bet, William Hill), also on the 1st and 2nd set and odd or even games, in "Odds lines" with source "flashscore"; during a match its in-play prices at the time of the run. Charged as "Flashscore odds" only for matches with odds.

## `oddsCountry` (type: `string`):

With "Add Flashscore odds": the country whose bookmakers are read (US-NJ and US-NY: a state).

## `oddsScopes` (type: `array`):

With "Add Flashscore odds": the whole match, the 1st set and the 2nd set (period match, set1, set2 in the odds lines).

## `minEdgePercent` (type: `number`):

Value bets: every odds line gets its fair price (Pinnacle without margin where Pinnacle has the market, else the bookmakers' consensus without margin), edgePercent and isBestPrice; the row gets bestEdgePercent, valueBetCount and surebetMarginPercent (below 0 = a surebet). With a number here only matches with a line at least this much above its fair price are saved (e.g. 3). Needs "Add match details" or "Add Flashscore odds". Matches below it are not saved or charged; the odds pages read for them are charged as "Extra page". Empty = every match, the lines are rated anyway.

## `includePredictionMarkets` (type: `boolean`):

Singles: the Kalshi and Polymarket prices of the match (probability of each player, bid and ask, volume, Polymarket set and total markets), their average and the edge against the bookmakers. Charged as "Prediction markets" only for matches with a market (mostly ATP, WTA and Challenger matches of the last weeks and the next days).

## `includeMatchStatistics` (type: `boolean`):

Finished and live matches of every tour (ATP, WTA, Challenger, ITF; singles and doubles): aces, double faults, first serve in and won, second serve won, break points won and saved, service and return points, winners, unforced errors, net points, total points, for the match and per set (WTA singles also with the duration). Charged as "Match statistics" only for matches with statistics.

## `includePointByPoint` (type: `boolean`):

Finished and live matches: every game with the score after it, who served, breaks, the points of the game with break, set and match points marked (and counted per game), tie-breaks with their points. Charged as "Match statistics" (once per match, also with "Add match statistics").

## `includeLiveState` (type: `boolean`):

Matches in progress: the set being played, who serves, the games of the set and the points of the current game (liveSet, liveServer, liveHomeGames, liveHomePoints...). Free.

## `includeElo` (type: `boolean`):

ATP and WTA singles: each player's current Elo rating overall and on the match's surface (Tennis Abstract, weekly; homeEloCurrent, homeSurfaceEloCurrent, eloDate), the win probability from them (overall, surface and their average) and its edge against the bookmakers. Today's rating, not the one at the time of an old match. One page per tour and run.

## `includeEspn` (type: `boolean`):

Grand Slams, ATP and WTA tour singles: ESPN's match and player IDs, the court and the venue (for joining with ESPN data). One ESPN page per tour and day.

## `includeRounds` (type: `boolean`):

The lists of days do not give the round: read it from each tournament's page (one page per tournament and run). Tournament and player pages have it anyway.

## `includePlayerCountries` (type: `boolean`):

Singles: each player's country from the profile (one page per player and run).

## `includeRankAtMatchTime` (type: `boolean`):

Singles: each player's rank in the official ranking of the week of the match (homeRankAtMatch, awayRankAtMatch, rankDate), not today's rank. Players ranked lower than "Rank depth" get null.

## `rankDepth` (type: `integer`):

With "Add rank at the time of the match": how deep in the ranking to look (300 = the top 300).

## `timezone` (type: `string`):

Time zone of the days of the input and of the local start time and match date (e.g. Europe/London, America/New_York). Start times are always also given in UTC.

## `outputFields` (type: `array`):

Save only these fields (names as in the output, e.g. homePlayer, awayPlayer, scoreText, oddsHome); id, rowType, url, source and scrapedAt are always kept. Empty = all fields.

## `csvExports` (type: `array`):

Also save the finished matches as CSV files in the column layouts tennis models read: Jeff Sackmann's match files (MATCHES-SACKMANN.csv) and tennis-data.co.uk (MATCHES-TENNIS-DATA.csv); links in the Output tab. Free. The values are this run's (statistics, ranks and odds only with their options).

## `maxItemsPerSource` (type: `integer`):

Maximum per URL, player season, tournament season or day. Empty = no limit.

## `onlyNewOrChanged` (type: `boolean`):

Return new matches, and matches whose status, score or start time changed, with the previous status and score; ranking rows and profiles whose rank, points or record changed.

## `monitoringKey` (type: `string`):

Name of the remembered state; use a different key for every saved search. Empty = "default".

## `monitorOdds` (type: `boolean`):

Also return matches whose average odds moved, with the previous odds.

## `minOddsChangePercent` (type: `number`):

With "Monitoring: odds changes": only odds that moved at least this much (default 2 %, 0 = every move).

## `onlyOddsAlerts` (type: `boolean`):

With "Monitoring: odds changes": return only matches whose odds moved at least the minimum change (no new matches, no score changes).

## `emitExpired` (type: `boolean`):

Also return scheduled or live matches that were on a list read in full last time and are no longer there (cancelled, withdrawn, moved), once each, with changeType "expired".

## `onlyNew` (type: `boolean`):

Return new matches only, not changed ones.

## `skipFirstRun` (type: `boolean`):

The first run only remembers the matches and returns nothing; later runs return what changed.

## `resetMonitoring` (type: `boolean`):

Forget the remembered matches of this Monitoring key.

## `telegramBotToken` (type: `string`):

Token of your bot from @BotFather.

## `telegramChatId` (type: `string`):

Chat, group or channel to send to (e.g. 123456789 or -1001234567890).

## `slackWebhookUrl` (type: `string`):

Incoming webhook (https://hooks.slack.com/...).

## `discordWebhookUrl` (type: `string`):

Webhook of your Discord channel (https://discord.com/api/webhooks/...). In Discord: channel settings → Integrations → Webhooks → Copy Webhook URL. Stored encrypted.

## `webhookUrl` (type: `string`):

Any HTTPS URL (Zapier, Make, n8n, your server): receives the matches as JSON.

## `whatsappAccessToken` (type: `string`):

Access token of the WhatsApp Cloud API of your Meta business account, used with "WhatsApp phone number ID" and "WhatsApp recipient number" (step by step in the README, section "WhatsApp notifications: setup"). For scheduled runs use a permanent token of a system user: Business settings → System users → Generate token, with the permissions whatsapp_business_messaging and whatsapp_business_management; the token of WhatsApp → API Setup expires within hours. Stored encrypted.

## `whatsappPhoneNumberId` (type: `string`):

ID of your WhatsApp business number that sends the message (not the number itself), e.g. 106540352242922. In your Meta app: WhatsApp → API Setup → Phone number ID.

## `whatsappTo` (type: `string`):

Phone number that gets the message, in international format with the country code (e.g. +420601234567); up to 5 numbers separated by commas or new lines, each gets its own message and the notification is charged once per run. A test number of Meta sends only to numbers you added and confirmed under API Setup → To. Stored encrypted.

## `whatsappTemplateName` (type: `string`):

Name of your approved message template (WhatsApp Manager → Message templates, e.g. apify_results), recommended: WhatsApp delivers a template message at any time. Its body gets the run summary with the first results in {{1}} and the dataset link in {{2}} (a template with only {{1}} gets both in {{1}}). Empty: a plain text message, which WhatsApp delivers only when the recipient wrote to your business number in the last 24 hours, so a scheduled run usually needs a template. Meta charges your business account for template messages (step by step in the README, section "WhatsApp notifications: setup").

## `whatsappTemplateLanguage` (type: `string`):

Language code of the template exactly as WhatsApp Manager → Message templates shows it next to the template, e.g. en_US, en_GB, cs, sk, pl or de. Used only with "WhatsApp template name".

## `notificationLimit` (type: `integer`):

How many matches the message lists.

## `notifyOnlyChanges` (type: `boolean`):

No message after a run that saved nothing.

## `maxRequestsPerMinute` (type: `integer`):

How fast the actor reads TennisExplorer (default 90, at most 180).

## `maxConcurrency` (type: `integer`):

How many pages the actor reads at the same time (default 4, at most 6).

## `proxyConfiguration` (type: `object`):

No proxy needed. TennisExplorer is not available from the Czech Republic: with your own proxy, use another country. A run through a residential proxy may be charged a little more to cover its traffic.

## `exportFormats` (type: `array`):

Off by default. Printable HTML report: the results as a clean, branded table with the main columns, made for printing, saving as PDF or sending to someone; for working with the data use Excel or CSV, which have every field. Markdown table: the same columns as text for AI tools, docs or GitHub. The Output tab links the files. Each file has the overview columns of every saved row and nothing is left out, so a run with tens of thousands of rows makes a file of tens of MB that can be slow to open; for big runs use the dataset or its Excel export. Excel (XLSX), CSV and JSON are always in the Output tab and under Export, at no extra cost.

## `sendErrorReports` (type: `boolean`):

When a run fails, send the developer a short error report: the error and your input with secrets left out (tokens, webhooks and e-mails are hidden). Your results are never sent. Reports are deleted after at most 120 hours. Turn off to send nothing.

## Actor input object example

```json
{
  "dateFrom": "yesterday",
  "matchTypes": [
    "atp-single"
  ],
  "maxItems": 20,
  "includePlayerProfile": true,
  "includeQualificationDraws": false,
  "rankingSort": "rank",
  "includeRankingProfiles": false,
  "maxRank": 100,
  "onlyMovers": false,
  "bettingRankingType": "best",
  "excludeQualification": false,
  "onlyWithOdds": false,
  "includeMatchDetails": false,
  "includeInjuries": false,
  "h2hLimit": 10,
  "oddsMarkets": [
    "winner"
  ],
  "includeOddsHistory": false,
  "oddsFormat": "decimal",
  "includeFlashscoreOdds": false,
  "oddsCountry": "GB",
  "oddsScopes": [
    "FULL_TIME",
    "FIRST_SET",
    "SECOND_SET"
  ],
  "includePredictionMarkets": false,
  "includeMatchStatistics": false,
  "includePointByPoint": false,
  "includeLiveState": false,
  "includeElo": false,
  "includeEspn": false,
  "includeRounds": false,
  "includePlayerCountries": false,
  "includeRankAtMatchTime": false,
  "rankDepth": 300,
  "timezone": "UTC",
  "csvExports": [],
  "onlyNewOrChanged": false,
  "monitorOdds": false,
  "minOddsChangePercent": 2,
  "onlyOddsAlerts": false,
  "emitExpired": false,
  "onlyNew": false,
  "skipFirstRun": false,
  "resetMonitoring": false,
  "whatsappTemplateLanguage": "en_US",
  "notificationLimit": 10,
  "notifyOnlyChanges": true,
  "maxRequestsPerMinute": 90,
  "maxConcurrency": 4,
  "proxyConfiguration": {
    "useApifyProxy": false
  },
  "exportFormats": [],
  "sendErrorReports": true
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `excel` (type: `string`):

All saved rows as an Excel file, with every field.

## `htmlReport` (type: `string`):

The saved rows with the main columns as a clean table to print, save as PDF or send; only when "Extra export formats" includes it. Excel has every field.

## `markdown` (type: `string`):

The saved rows as a Markdown table, handy for AI tools, docs and GitHub; only when "Extra export formats" includes Markdown.

## `sackmannCsv` (type: `string`):

The finished matches as CSV in the columns of Jeff Sackmann's match files; only when "Match files for models" includes it.

## `tennisDataCsv` (type: `string`):

The finished matches as CSV in the columns of tennis-data.co.uk (sets, ranks, B365, Pinnacle, max and average odds); only when "Match files for models" includes it.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "dateFrom": "yesterday",
    "matchTypes": [
        "atp-single"
    ],
    "maxItems": 20,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("tsutseisoftware/tennisexplorer-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "dateFrom": "yesterday",
    "matchTypes": ["atp-single"],
    "maxItems": 20,
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("tsutseisoftware/tennisexplorer-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "dateFrom": "yesterday",
  "matchTypes": [
    "atp-single"
  ],
  "maxItems": 20,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call tsutseisoftware/tennisexplorer-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tsutseisoftware/tennisexplorer-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/771ScYSMzV4iLOaMY/builds/JqjNAeAmPBQQ9fcS5/openapi.json
