Tennis Scores and Results Scraper: ATP, WTA, Odds, Rankings
Scrape tennis scores: ATP and WTA match results of any day with set by set scores, tiebreaks, winner and pre-match odds, the day's schedule, current WTA singles or doubles rankings, or the WTA season calendar. Sources: tennisexplorer.com and wtatennis.com public pages.
- on apify
v0iddo/tennis-scores-api- category
- automation
- build
- 0.1.3, built 2026-11-15
- billing
- Apify bills it per result; the price for your plan is on the actor's page.
What you get
Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API.
The main fields of each row:
datetime- Tournament (
tournamentName) - Player 1 (
player1) - Player 2 (
player2) scorewinner- Odds 1 (
odds1) - Odds 2 (
odds2) rank- Player (
playerName) - Ranking Points (
rankingPoints) toururl
What people use it for
- Score feeds: every finished ATP and WTA match of a day with set scores, tiebreaks, winner and start time in UTC.
- Betting models: pre-match odds of both players next to the result, for back tests over many days.
- Match previews: the day's schedule with start times, seeds and odds for singles and doubles.
- Sports media: current WTA rankings with points and the WTA season calendar for weekly tables.
Run it on Apify
- Open tennis-scores-api on Apify and sign in, or make an Apify account.
- On the Input tab, fill in the fields listed below. The form opens with example values filled in.
- Click Start. Rows appear on the Output tab while the run works.
- Export the rows as JSON, CSV, Excel, XML or HTML, or read them through the Apify API.
- To run it again on a schedule, save the input as a task and add a schedule in the Apify Console.
What you can set
- Data type (
dataType): match_results: finished matches of a day with set scores, winner and odds. upcoming_matches: the schedule of a day with start times and odds. wta_rankings: current WTA player rankings with ranking points. wta_tournaments: the WTA season calendar with dates. Options: match_results, upcoming_matches, wta_rankings, wta_tournaments. Default:match_results. - Tour and event (
matchType): Which matches to read: all (ATP and WTA, singles and doubles), atp-single, wta-single, atp-double, wta-double, singles (both tours) or doubles (both tours). ATP includes Challenger events. Applies to match_results and upcoming_matches. Options: all, atp-single, wta-single, atp-double, wta-double, singles, doubles. Default:all. - Date (
date): Day to read as YYYY-MM-DD. Empty: yesterday for match_results, today for upcoming_matches (the site's day, GMT+1). - Days (
days): Number of days to read: match_results goes back from Date, upcoming_matches goes forward from it. 0 or 1: that day only. Default:1. - Ranking type (
rankingType): Singles or doubles ranking. Applies only when dataType is wta_rankings. Options: singles, doubles. Default:singles. - Pages to read (
maxPages): Number of ranking list pages to fetch. Each page lists approximately 20 players. Default:3. - Maximum results (
maxItems): The run stops after this many result rows. It also caps what one run can cost. Default:100. - Proxy configuration (
proxyConfiguration): Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network.
Example input
This is the input the actor is tested with every day.
{
"dataType": "match_results",
"matchType": "all",
"days": 1,
"maxItems": 20
}Run it from Python
The official apify-client package starts the run, waits for it and reads the rows. It needs your own Apify API token.
# pip install apify-client
from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN") # your own API token, from the Apify Console
run_input = {
"dataType": "match_results",
"matchType": "all",
"days": 1,
"maxItems": 20,
}
run = client.actor("v0iddo/tennis-scores-api").call(run_input=run_input)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)Limits
- Match results (the default) list every finished ATP and WTA match of the day, Challenger events included, with the winner first: set by set games, a tiebreak as 7-6(5), sets won and the two pre-match odds where the site shows them (smaller events often have none).
- Times are the site's (GMT+1, as tennisexplorer.com shows them); startTimeUtc gives the same start in UTC. Doubles rows name both players of each team. status is finished, retired, walkover, scheduled, or started for a schedule row whose match is under way.
- Rankings (dataType wta_rankings) cover active WTA tour professionals, about 20 players a page; the WTA calendar (wta_tournaments) lists the season's events with start and end dates.
- Data reflects what the sites publish at the time of collection; a match in progress is not followed live.
- Not affiliated with the Women's Tennis Association, wtatennis.com or tennisexplorer.com.
- Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
- The actor reads only pages that the site's robots.txt leaves open to automated access.
- Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
- Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.
Questions
Do I need an account on tennisexplorer.com and wtatennis.com, cookies or an API key?
No. The actor reads only what every visitor of tennisexplorer.com and wtatennis.com can see, without logging in. You only need an Apify account to start it.
How many results can one run return?
Up to 5,000 rows per run. Without a limit it stops at 100. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.
Why did my run return no results?
The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.
Can I run it on a schedule?
Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.
Which formats can I export?
JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.
More
every fact here is read from the actor's public data on Apify, every day; it last changed on