# Tennis Scraper - Live Scores, ATP & WTA Rankings (`oddsmith/tennis-scraper-live-scores-rankings`) Actor

Live tennis in one schema: in-play scores set by set, full ATP and WTA rankings with points and rank movement, and tournament schedules with past champions. Both tours share field names, so you can stack them without remapping. Keyless, no browser, and never charged for empty results.

- **URL**: https://apify.com/oddsmith/tennis-scraper-live-scores-rankings.md
- **Developed by:** [oddsmith Data](https://apify.com/oddsmith) (community)
- **Categories:** Sports, News, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 ranking rows

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 Scraper — Live Scores, ATP & WTA Rankings

Live tennis in one clean schema: in-play match scores, the full ATP and WTA singles rankings, and tournament schedules. No API key, no login, no browser.

### What you get

| Mode | Returns |
|------|---------|
| **Live matches** | Every in-play match with set-by-set scores, current game, server, surface, round, and both players' world rankings and seeds |
| **ATP / WTA rankings** | Up to 500 players per tour with points, previous rank, and positions gained or lost |
| **Tournaments** | Tournament schedule and status, including Grand Slam flags and past champions |

### Why this Actor

- **Both tours, one schema.** ATP and WTA records share field names, so you can stack them without remapping.
- **Rank movement included.** Rankings carry previous position and computed change, not just today's number.
- **You are never charged for nothing.** Incomplete records are skipped, not billed.
- **No key, no login, no browser.** Public endpoints only.

### Example input

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

Full rankings for both tours:

```json
{ "mode": "rankings", "tours": ["atp", "wta"], "maxItems": 500 }
```

### Pricing

Pay per record delivered. Nothing else is billed — no platform usage charge on top.

| Event | Price | What one record is |
|---|---|---|
| `ranking-item` | **$1.00 / 1,000** | One ATP or WTA ranking row |
| `match-item` | **$3.00 / 1,000** | One live match with per-set scores |
| `tournament-item` | **$3.00 / 1,000** | One tournament with dates and past champions |

Typical runs, measured on the platform:

| Run | Records | Cost |
|---|---|---|
| Full ATP + WTA rankings | 1,000 | **$1.00** |
| Live matches, mid-afternoon | ~23 | **~$0.07** |
| Tournaments, both tours | ~5 | **~$0.02** |

### Notes

- Set scores appear as `home_sets` / `away_sets` plus per-set detail in `home_sets_detail`.
- `ground_type` gives the surface (Hard, Clay, Grass) where the source publishes it.
- Live mode returns whatever is in play at run time; during off-hours that can legitimately be zero matches, and zero results cost you nothing.
- Fields the source does not publish come back as `null` rather than being dropped, so the columns are stable across runs. Doubles pairs have no individual ranking or country, and not every draw publishes a round.

# Actor input Schema

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

What to pull. 'live' returns in-play matches with current set and game scores; 'rankings' returns the ATP and/or WTA singles rankings; 'tournaments' returns tournament-level schedule and status.

## `tours` (type: `array`):

Which tours to include for rankings and tournaments modes. Ignored in live mode, which returns every in-play match.

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

Upper bound on delivered records per tour. Rankings return up to 500 players per tour.

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

Optional date filter for tournaments mode, formatted YYYYMMDD, for example 20260828. Leave blank for the current schedule.

## Actor input object example

```json
{
  "mode": "live",
  "tours": [
    "atp",
    "wta"
  ],
  "maxItems": 500
}
```

# Actor output Schema

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

All records from this run, in the default dataset. Export as JSON, CSV or Excel.

# 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("oddsmith/tennis-scraper-live-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("oddsmith/tennis-scraper-live-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 '{}' |
apify call oddsmith/tennis-scraper-live-scores-rankings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,oddsmith/tennis-scraper-live-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/JNQANSZLwQ1URbfpH/builds/aUpSaPYWHhn1xNa9E/openapi.json