# Tennis Odds and Results Scraper (`dektionstudio/tennis-odds-scraper`) Actor

Tennis matches by date with average betting odds for each player: ATP, WTA, Challenger, ITF and UTR events, set scores with tiebreaks, seeds, winners and start times. Results and upcoming matches, up to 31 days per run. $1 per 1,000 matches.

- **URL**: https://apify.com/dektionstudio/tennis-odds-scraper.md
- **Developed by:** [Dektion Studio](https://apify.com/dektionstudio) (community)
- **Categories:** Sports, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 matches

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Tennis Odds and Results Scraper

Tennis matches by date with the average betting odds for each player, from the ATP and WTA tours down to Challengers, ITF events and the UTR Pro Tennis Series. Each match also has both players and their seeds, the set scores with tiebreaks, the winner and the start time. Finished results and upcoming matches, for one day or up to 31 days in one run.

It reads TennisExplorer's daily match pages, which list every match of the day with average odds, including the smaller Challenger and ITF events many sources skip. 20 September 2026 alone had 549 matches, every one with odds, and nearly half were men's ITF Futures. For a tennis model or a betting sheet, that's the same columns every day without copying tables by hand.

### What you get for each match

- Date, local start time (Central European, as the site shows it) and start time in UTC
- Tournament and its page, country, level (ATP, WTA, Challenger, ITF, or UTR for the UTR Pro Tennis Series), men or women, singles or doubles
- Both players with their profile links and seeds
- Sets won, the score of every set with tiebreak points, and the winner
- Average betting odds for each player, before the match
- Status: finished, walkover or scheduled, and a link to the match page

### Input

```json
{
    "startDate": "2026-09-01",
    "endDate": "2026-09-26",
    "levels": ["ATP", "WTA"],
    "status": "finished",
    "players": ["Sinner", "Swiatek"]
}
```

- Leave the dates empty to get today's matches. Schedule a daily run for a steady feed of results and odds.
- `levels`, `status`, `players`, `tournaments` and `withOddsOnly` filter the matches before you pay for them.
- Player names are written the way the site writes them, surname first, so `Sinner` or `Swiatek` matches.

### Output

```json
{
    "date": "2026-09-26",
    "localTime": "08:55",
    "startTime": "2026-09-26T06:55:00.000Z",
    "tournament": "Chengdu",
    "tournamentUrl": "https://www.tennisexplorer.com/chengdu/2026/atp-men/",
    "country": "CN",
    "level": "ATP",
    "gender": "men",
    "format": "singles",
    "player1": {
        "name": "Hurkacz H.",
        "url": "https://www.tennisexplorer.com/player/hurkacz/",
        "seed": "5"
    },
    "player2": {
        "name": "Damm M.",
        "url": "https://www.tennisexplorer.com/player/damm-4f98a/",
        "seed": null
    },
    "setsWon": [
        2,
        1
    ],
    "sets": [
        {
            "player1": 4,
            "player2": 6,
            "tiebreak": null
        },
        {
            "player1": 6,
            "player2": 3,
            "tiebreak": null
        },
        {
            "player1": 6,
            "player2": 4,
            "tiebreak": null
        }
    ],
    "winner": 1,
    "odds": {
        "player1": 1.4,
        "player2": 2.91
    },
    "matchStatus": "finished",
    "matchUrl": "https://www.tennisexplorer.com/match-detail/?id=3332288"
}
```

### Pricing

$0.001 per match, so a full day of around 500 matches costs about $0.50 and ATP and WTA singles alone cost much less. Filters apply before charging, and a day that can't be read is an error row that costs nothing. Apify adds $0.00005 per run for starting the Actor.

### Limits

- The odds are the average the site shows for each player, not every bookmaker's line.
- Live scores aren't covered: a match shows up as scheduled until it's finished.
- Point-by-point data and match statistics (aces, break points) aren't included.
- Walkovers come back with the winner and no set scores.

### Changelog

- 2026-09-27: first version.

# Actor input Schema

## `startDate` (type: `string`):

First day, like 2026-09-20. Empty means today (Central European time).

## `endDate` (type: `string`):

Last day. Empty means the same as the first day. Up to 31 days per run.

## `matchType` (type: `string`):

Which matches to read.

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

Keep only these tour levels. Empty keeps all.

## `status` (type: `string`):

Results, upcoming matches, or both.

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

Keep matches with any of these players, by name as the site writes it (surname first, like Sinner or Swiatek).

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

Keep matches from tournaments whose name contains any of these, like Shanghai or Wimbledon.

## `withOddsOnly` (type: `boolean`):

Skip matches without betting odds.

## Actor input object example

```json
{
  "startDate": "2026-09-20",
  "matchType": "all",
  "levels": [
    "ATP",
    "WTA"
  ],
  "status": "all",
  "withOddsOnly": false
}
```

# Actor output Schema

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

No description

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

No description

# 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 = {
    "startDate": "2026-09-20",
    "levels": [
        "ATP",
        "WTA"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("dektionstudio/tennis-odds-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 = {
    "startDate": "2026-09-20",
    "levels": [
        "ATP",
        "WTA",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("dektionstudio/tennis-odds-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 '{
  "startDate": "2026-09-20",
  "levels": [
    "ATP",
    "WTA"
  ]
}' |
apify call dektionstudio/tennis-odds-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dektionstudio/tennis-odds-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/NSjkISYUbTbkYCiEz/builds/EcL7S7YnFAg0MjP7v/openapi.json