# Tennis Scores: ATP & WTA Results, Fixtures & Rankings (`tacps126/tennis-scores-rankings`) Actor

ATP and WTA tennis results, live scores and fixtures: set-by-set scores with tiebreaks, round and draw, singles and doubles, walkovers and retirements, plus singles rankings with points and moves. Results once on a schedule.

- **URL**: https://apify.com/tacps126/tennis-scores-rankings.md
- **Developed by:** [Tapaswai Choudhary](https://apify.com/tacps126) (community)
- **Categories:** Sports, Automation, Developer tools
- **Security:** Limited permissions
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.40 / 1,000 match or ranking rows

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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

## Tennis Scores: ATP & WTA Results, Fixtures & Rankings

**ATP and WTA tennis** in one table: **results and live scores** with **set-by-set scores and tiebreaks**, the **order of play** for the coming days, **singles and doubles**, walkovers and retirements, plus **ATP and WTA singles rankings** with points and moves. Filter by player, draw and status, export to JSON, CSV or Excel, or schedule it to get each result once.

**Built for** tennis bettors and modellers, fantasy players, tennis media and newsletters, app and bot builders, researchers, and AI agents.

### What you get

**Matches** (one row per match):

| Field | Meaning |
|---|---|
| `league` (ATP, WTA), `eventName`, `venue`, `draw`, `session` | Tour, tournament, place, draw (e.g. Men's Singles, Women's Doubles) and round |
| `date`, `status`, `state` (pre, in, post), `completed`, `statusDetail` | When, and where it stands (Final, Walkover, Retired, In Progress, Scheduled) |
| `name`, `winner`, `result` | Both sides, the winner, and the result line with seeds and set scores, e.g. `(5) Alex de Minaur (AUS) bt Matteo Berrettini (ITA) 7-6 (7-4) 6-2` |
| `competitors` | Each player or doubles pair with `country`, `lineScores` (games per set), `winner`, and for doubles both `players` with their countries |
| `eventId`, `competitionId`, `url` | Ids and the match link |

```json
{
  "league": "ATP",
  "eventName": "Erste Bank Open",
  "draw": "Men's Singles",
  "session": "Quarterfinal",
  "name": "Alex de Minaur vs Matteo Berrettini",
  "status": "Final",
  "winner": "Alex de Minaur",
  "result": "(5) Alex de Minaur (AUS) bt Matteo Berrettini (ITA) 7-6 (7-4) 6-2",
  "competitors": [
    { "name": "Alex de Minaur", "country": "Australia", "lineScores": [7, 6], "winner": true },
    { "name": "Matteo Berrettini", "country": "Italy", "lineScores": [6, 2], "winner": false }
  ]
}
```

**Rankings** (one row per player, ATP and WTA singles top 150): `position` (current rank), `team` (player), `teamId`, `country`, `age`, `rankingDate`, and `stats` with `points`, `previous` rank and `trend` (e.g. `+2`).

### Why this Actor

- **Men's and women's tours, singles and doubles**, with the same fields.
- **Set scores and tiebreaks**, plus walkovers and retirements marked in `status`.
- **Fixtures too**: days ahead for the coming order of play.
- **Rankings** with points and weekly moves.
- **Results once**: *Only new* + a daily schedule returns each match again only when its status changes, so finals arrive once.
- **For AI agents.** Callable as an MCP tool.

### How to use it

Yesterday's and today's finished singles matches:

```json
{ "daysBack": 1, "gameStatus": "final", "matchType": "singles" }
```

The next three days' matches:

```json
{ "daysBack": 0, "daysAhead": 3, "gameStatus": "scheduled" }
```

Every match Sinner and Swiatek played this season:

```json
{ "dateFrom": "2026-01-01", "teams": ["Sinner", "Swiatek"] }
```

Current ATP and WTA singles rankings:

```json
{ "dataType": "standings" }
```

### Options

| Option | What it does |
|---|---|
| **Tours** (`leagues`) | `atp`, `wta` |
| **Data** (`dataType`) | `games` (matches) or `standings` (rankings) |
| **Days back** / **Days ahead** (`daysBack`, `daysAhead`) | Rolling window: `daysBack: 1` = yesterday and today; `daysAhead: 3` = the next three days |
| **From date** / **To date** (`dateFrom`, `dateTo`) | Exact range (`YYYY-MM-DD`), up to about one season per run |
| **Match status** (`gameStatus`) | `any`, `final`, `live` or `scheduled` |
| **Players** (`teams`) | Player names, e.g. `Sinner`, `Alcaraz`. Empty = all |
| **Draw** (`matchType`) | `any`, `singles` or `doubles` |
| **Max results** (`maxItems`) | Most rows per run |
| **Only new** (`onlyNew`, `monitorName`) | With a schedule, each run returns only rows earlier runs did not deliver; a match comes again when its status changes |

### Pricing

**$3 per 1,000 matches or ranking rows**, plus a small start fee per run. On the Apify free plan a run returns up to 100 rows.

### Good to know

- Covers ATP and WTA tour events and Grand Slams, qualifying included. Challenger and ITF events are not included.
- Rankings are the latest published singles list (updated weekly); past weeks are not available.
- Need other sports? **Sports Data** (tacps126/sports-data) covers 24 leagues with the same fields.
- Questions: **tacps126@gmail.com**.

# Actor input Schema

## `leagues` (type: `array`):

ATP (men) and/or WTA (women): tour-level events and Grand Slams.

## `dataType` (type: `string`):

Matches give both players or pairs, set scores with tiebreaks, round, draw, status, venue and the result line. Rankings give rank, points, previous rank and move, age and country.

## `daysBack` (type: `integer`):

1 = yesterday and today.

## `daysAhead` (type: `integer`):

Upcoming matches, e.g. 3 for the next three days' order of play.

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

YYYY-MM-DD; replaces Days back.

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

YYYY-MM-DD; replaces Days ahead. Up to about one season per run.

## `gameStatus` (type: `string`):

Final includes walkovers and retirements.

## `teams` (type: `array`):

Player names, e.g. Sinner, Swiatek, Alcaraz. Empty = all.

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

Singles, doubles or both.

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

Most rows returned per run.

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

Schedule the Actor and each run returns only what earlier runs did not deliver. A match comes again when its status changes (scheduled, live, final), so a daily run with Match status = Final gives each result once.

## `monitorName` (type: `string`):

Optional name for the "only new" history, so several monitors can run side by side.

## `tenantId` (type: `string`):

Optional label used to keep separate histories for different clients or teams.

## `debug` (type: `boolean`):

Save extra diagnostics with the run (for support requests).

## Actor input object example

```json
{
  "leagues": [
    "atp",
    "wta"
  ],
  "dataType": "games",
  "daysBack": 1,
  "daysAhead": 0,
  "gameStatus": "any",
  "matchType": "any",
  "maxItems": 1000,
  "onlyNew": false,
  "debug": false
}
```

# Actor output Schema

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

The produced items (default dataset items).

# 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 = {
    "leagues": [
        "atp",
        "wta"
    ],
    "daysBack": 1
};

// Run the Actor and wait for it to finish
const run = await client.actor("tacps126/tennis-scores-rankings").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 = {
    "leagues": [
        "atp",
        "wta",
    ],
    "daysBack": 1,
}

# Run the Actor and wait for it to finish
run = client.actor("tacps126/tennis-scores-rankings").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 '{
  "leagues": [
    "atp",
    "wta"
  ],
  "daysBack": 1
}' |
apify call tacps126/tennis-scores-rankings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tacps126/tennis-scores-rankings"
        }
    }
}
```

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/iUHgOOuttG9bM2tAO/builds/91dcsM0blpMnQbVkz/openapi.json
