# Tennis Matches + Odds, Form & Head-to-Head \[$0.02/match] (`perchpermits/tennis-matches-odds-form`) Actor

ATP and WTA matches for any day, live or finished, with 15+ bookmakers' opening and current odds, rankings, last-10 form, surface record, and head-to-head in one JSON row per match. Filter by tour, tournament, player. Built for betting models and AI agents. $0.02 per enriched match.

- **URL**: https://apify.com/perchpermits/tennis-matches-odds-form.md
- **Developed by:** [Perch Data](https://apify.com/perchpermits) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 match with odds, form and head-to-heads

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Tennis Matches + Odds, Form & Head-to-Head (ATP/WTA)

One JSON row per tennis match with everything a betting model or an AI agent asks for before it prices a match, in a single call:

- **The match**: date, start time in UTC, tournament, tour (ATP/WTA), round, surface, both players with seeds, status (scheduled, in progress, finished), and the score with tiebreaks.
- **Odds**: the site's reference odds on the list, plus, when enriched, 15+ bookmakers' **current and opening** odds per player, the trend since opening, the best available price and who offers it, and optionally the full timestamped movement history.
- **Form**: each player's last N matches (opponent, round, date, score, won/lost), a W/L sequence like `WWLWW`, the current streak, and this year's win/loss record by surface.
- **Head-to-head**: the total and every previous meeting with year, tournament, surface, round, and score.
- **Rankings and bio**: singles rank, birthdate, height, weight, handedness.

Other tennis actors on the store sell one of those pieces each. This one joins them so an agent does not need four actors and a merge step.

Source: TennisExplorer, public pages, no login. Coverage is ATP, WTA, Challenger, ITF, and UTR events. Nothing is guessed; missing values are `null`.

### Quick start

Today's ATP singles with odds, form, and head-to-head:

```json
{ "tour": "atp" }
```

Every match at a tournament over the next three days, plain rows only (cheapest):

```json
{ "tournament": "US Open", "days": 3, "enrich": false, "maxMatches": 500 }
```

Yesterday's finished WTA results with closing odds and the score:

```json
{ "mode": "results", "date": "2026-09-08", "tour": "wta", "enrich": false }
```

Everything in progress right now, with current set scores and live bookmaker prices:

```json
{ "mode": "live" }
```

One player's next match with the full odds movement from every bookmaker:

```json
{ "player": "Alcaraz", "days": 7, "status": "scheduled", "oddsHistory": true, "maxMatches": 1 }
```

### Input

| Field | Type | Notes |
|---|---|---|
| `mode` | `schedule` | `results` | `live` | Schedule lists upcoming, live, and completed matches of the day. Results lists finished matches only. Live lists matches in progress right now with the current set scores, a snapshot as of `fetched_at_utc`; it ignores `date` and `days`. Default `schedule`. |
| `date` | `YYYY-MM-DD` | Defaults to today. The site's day runs on Central European time. |
| `days` | 1 to 14 | Consecutive days starting at `date`. Default 1. |
| `tour` | `all` | `atp` | `wta` | Default `all`. |
| `doubles` | boolean | Doubles instead of singles. Default false. |
| `tournament` | string | Case-insensitive substring of the tournament name. |
| `player` | string | Case-insensitive substring of either player's name. |
| `status` | `scheduled` | `in_progress` | `finished` | Keep only one state. |
| `maxMatches` | integer | Stop after this many. Default 50. |
| `enrich` | boolean | Fetch each match's detail page. Default true. One request per match, about a second each. |
| `latestMatches` | 1 to 30 | Recent matches per player when enriching. Default 10. |
| `oddsHistory` | boolean | Include every recorded odds change per bookmaker. Default false. |
| `preview` | boolean | Add a written `preview` to each enriched row (below). Default false. Charged as `match-preview` on top of `enriched-match`. |
| `requestDelaySeconds` | number | Politeness delay toward the source. Default 0.4. |

### Output

Every row has these top-level fields:

| Field | Meaning |
|---|---|
| `match_id`, `match_url` | Source identifiers. |
| `date`, `time_site`, `start_utc` | Calendar day and start time as listed (Central European time) and converted to UTC. |
| `fetched_at_utc` | When this row was read from the source. Age a live or odds snapshot with it. |
| `status` | `scheduled`, `in_progress`, or `finished`. |
| `tournament` | `name`, `url`, `slug`, `year`, `tour` (`atp`/`wta`), `format` (`singles`/`doubles`). |
| `round`, `surface` | From the detail page (enriched rows only). |
| `home`, `away` | `name`, `slug`, `url`, `seed`. "Home" is the first-listed player. |
| `odds` | Reference odds from the list page: `home`, `away` (decimal). |
| `h2h_list` | Head-to-head count as shown on the schedule list, when present. |
| `result` | `winner` (`home`/`away`), `sets_home`, `sets_away`, `sets[]` with `home`, `away`, `tiebreak_loser_points`, and `score` like `5-7, 3-6, 7-5, 6-3, 7-6(6)`. |
| `result_note` | `retired_or_walkover` when a finished match ended short. |

With `enrich` (default), the `enrichment` block adds:

| Field | Meaning |
|---|---|
| `status` | `ok`, `partial` (page found but no odds and no recent matches), `parse_failed`, `fetch_failed`. Only `ok` and `partial` rows are charged as enriched. |
| `home`, `away` | `full_name`, `singles_rank`, `birthdate`, `height`, `weight`, `plays`, `turned_pro`, `surface_record` (this year's `{wins, losses}` per surface), `form` (`played`, `wins`, `losses`, `streak` like `4W`, `sequence` like `WWWWL`), `latest_matches[]` (`date`, `tournament`, `round`, `round_full`, `opponent`, `won`, `sets`, `score`, `match_id`). |
| `h2h` | `home_wins`, `away_wins`, `matches[]` with `year`, `tournament`, `surface`, `round`, `winner_name`, `loser_name`, `score`, `match_id`. |
| `bookmakers[]` | Per bookmaker: `home`, `away` (current decimal odds), `home_opening`, `away_opening`, `home_trend`, `away_trend` (`up`/`down`), and with `oddsHistory` the `home_history[]`/`away_history[]` of `{at_site, odds, change}`. |
| `bookmaker_count`, `best_odds` | How many books priced the match, and the highest `home`/`away` price with the bookmaker offering it. |
| `market` | Derived from every bookmaker that priced both sides: `consensus_home`/`consensus_away` (mean odds), `fair_prob_home`/`fair_prob_away` (implied probabilities with the margin removed), `overround`, `favorite`, `opening_consensus_*`, `opening_fair_prob_home`, and `prob_shift_home` (how far the fair probability moved since opening; negative means the market turned against the first player). |
| `final_score` | For finished matches, the detail page's own score line, e.g. `2 : 1 (4-6, 6-4, 7-6(8))`. |
| `home.partner`, `away.partner` | Doubles only: the second player of each pair. Rankings and bio describe the first-listed player. |

With `preview: true`, each enriched row also carries:

| Field | Meaning |
|---|---|
| `preview` | `{text, model, generated_at}`: 90 to 140 words written by Claude from the row's own numbers: what the market prices and how it moved, then which of the form, surface, ranking, and head-to-head facts support or cut against that price. It names no winner and recommends nothing; a null field in the row is reported as missing, never guessed. `null` when the model could not produce one (that row is not charged the preview event). Absent when `preview` is off or the budget ran out. |

### Pricing

Pay per event. Free-tier credit covers a few hundred matches.

| Event | Price | When |
|---|---|---|
| `enriched-match` | $0.02 | A match row with the `enrichment` block (odds, form, head-to-head). |
| `match` | $0.002 | A plain match row (`enrich: false`, or the budget ran out). |
| `match-preview` | $0.10 | An enriched row that also carries a written `preview`. Charged in addition to `enriched-match`, only for rows where `preview` is not null. |

If `maxTotalChargeUsd` is set, the actor works out up front how many matches it can enrich within the budget, enriches those, and returns the rest plain; previews are capped the same way after enrichment. A run is never charged for rows it did not return. Failed enrichment (site error, layout change) is returned plain and charged as `match`.

### Use it from Zapier or Clay

No code needed; both call the actor with your own Apify account and you pay the per-row prices above. In Zapier, a **Schedule** trigger each morning, the Apify action **Run Actor** (synchronous) with `{ "mode": "schedule", "tour": "atp", "enrich": true, "maxMatches": 30 }`, then **Fetch Dataset Items** into a Google Sheet, a Slack channel, or a Notion database gives you the day's card with odds and form before play starts. In Clay, **Import data from Apify Actor** with the same input fills a table with one match per row.

### Wrap this in an afternoon

Reselling these rows behind your own search box is allowed and expected; it is what the per-row price is for. A zero-dependency starter kit does it: a one-page storefront, Stripe credit packs that never expire (no subscription), and one call to this actor per search. Point it at `perchpermits/tennis-matches-odds-form`, set your price per row, and deploy anywhere Node runs. Source and setup: [wrapper-kit](https://github.com/101NUTS/perchpermits-actors/tree/master/wrapper-kit). At $0.02 an enriched row here, a $0.10 charge per row on your side leaves about 80% before Stripe's fee.

### Limits and honesty

- Times are converted from Central European time to UTC. If the source changes its display timezone the `start_utc` values shift; `time_site` is always the raw value.
- Live scores are set-level snapshots at run time, not a point-by-point stream. Run again for an update; `fetched_at_utc` tells you how old a row is.
- If every enrichment in a run fails, the run fails and nothing is charged, so a blocked or changed source never turns into silent plain rows at the enriched price.
- The source does not publish match statistics (aces, serve percentages) on these pages, so none are returned.
- Odds are the bookmakers' listed prices at the time the source recorded them; they are for information, not a betting instruction. Check your local law before acting on them.
- If the source changes its layout the run fails loudly with `Source drift detected` and nothing is charged, rather than returning empty rows.

### Support

Open an issue on the actor page. Layout changes at the source are fixed within days.

# Actor input Schema

## `mode` (type: `string`):

`schedule` lists the day's upcoming, live, and completed matches. `results` lists only finished matches for the day. `live` lists only matches in progress right now, with the current set scores (a snapshot; run again for an update). `live` ignores `date` and `days`.

## `date` (type: `string`):

ISO date (YYYY-MM-DD). Defaults to today (UTC). Dates are the site's Central European calendar day.

## `days` (type: `integer`):

How many consecutive days to list, starting at `date`. 1 to 14.

## `tour` (type: `string`):

ATP (men), WTA (women), or both. Includes Challenger, ITF, and UTR events listed under each tour.

## `doubles` (type: `boolean`):

Return doubles matches instead of singles.

## `tournament` (type: `string`):

Case-insensitive substring of the tournament name, e.g. `US Open`, `Challenger`, `Wimbledon`.

## `player` (type: `string`):

Case-insensitive substring of either player's listed name, e.g. `Alcaraz`.

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

Keep only matches in this state. Leave empty for all.

## `maxMatches` (type: `integer`):

Stop after this many matches. Each enriched match is one extra request (about one second).

## `enrich` (type: `boolean`):

Fetch every match's detail page: round, surface, rankings, this year's W/L by surface, head-to-head history, 15+ bookmakers' current and opening odds, both players' latest matches and form. Charged as `enriched-match` instead of `match`.

## `latestMatches` (type: `integer`):

How many recent matches to include for each player when enriching (1 to 30).

## `oddsHistory` (type: `boolean`):

Add every recorded odds change per bookmaker (timestamped, site time). Larger rows.

## `preview` (type: `boolean`):

Add a `preview` field to each enriched row: 90 to 140 words by Claude on what the row's own numbers say (market, movement, form, surface, head-to-head). No pick, no invented facts. Charged as `match-preview` on top of `enriched-match`, only for rows that got one. Needs `enrich`.

## `requestDelaySeconds` (type: `number`):

Politeness delay toward the source site. Lower is faster but risks throttling.

## `archiveDatasetName` (type: `string`):

Optional. Name of a dataset in your account to append every returned row to, so scheduled runs build a history that outlives run-data retention. Not charged again.

## Actor input object example

```json
{
  "mode": "schedule",
  "days": 1,
  "tour": "all",
  "doubles": false,
  "status": "",
  "maxMatches": 50,
  "enrich": true,
  "latestMatches": 10,
  "oddsHistory": false,
  "preview": false,
  "requestDelaySeconds": 0.4
}
```

# Actor output Schema

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

Every match from the run with the optional `enrichment` block (odds, form, head-to-head).

## `resultsCsv` (type: `string`):

The same rows flattened with dot-separated column names.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("perchpermits/tennis-matches-odds-form").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("perchpermits/tennis-matches-odds-form").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 '{}' |
apify call perchpermits/tennis-matches-odds-form --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,perchpermits/tennis-matches-odds-form"
        }
    }
}

```

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/MQlT9M70sKcPHalAe/builds/UeyTgc1xVBOiUUVbJ/openapi.json