Tennis Abstract Player Match Scraper

Export recent public Tennis Abstract match results for one player into structured JSON, CSV, Excel, or an API workflow. Get a clean match-level dataset with opponents, scores, tournament context, rankings, and the statistics displayed for each public result.

What you get

Every exported row is one recent player match. Use it to:

• Track a player’s latest opponents, scores, and results.
• Build a surface-aware tennis player match history dataset.
• Compare tournament, round, ranking, and tennis match statistics trends.
• Feed match history into spreadsheets, dashboards, or analytical agents.

Input recipes

Start with a small request:

{
  "playerSlug": "NovakDjokovic",
  "maxItems": 20
}

Use the player identifier from the public Tennis Abstract player URL. For example, the slug in a player URL ending in ?p=IgaSwiatek is IgaSwiatek.

Output example

{
  "playerSlug": "NovakDjokovic",
  "playerName": "Novak Djokovic",
  "date": "2025-01-24",
  "tournament": "Australian Open",
  "surface": "Hard",
  "round": "SF",
  "opponent": "Alexander Zverev",
  "result": "W",
  "score": "7-6(5) 6-3",
  "sourceUrl": "http://www.tennisabstract.com/cgi-bin/player-classic.cgi?p=NovakDjokovic"
}

Statistics and rankings are included when displayed by the source for that match; unavailable source values are null rather than guessed.

Input settings

Input	Description
playerSlug	Required Tennis Abstract player identifier from the public player URL.
maxItems	Maximum recent match rows to export, from 1 to 200. Start with 20.

Output fields

Field	Description
playerSlug / playerName	Requested player identifier and public display name.
date	Match date as displayed by the source.
tournament / tournamentUrl	Tournament name and public tournament link when available.
surface / round	Surface and tournament round.
playerRank / opponentRank	Public ranking values when shown.
opponent / opponentSlug / opponentCountry	Opponent identity and source-provided metadata.
result / score	Displayed result marker and match score.
dominanceRatio	Source-provided dominance ratio when available.
aceRate / doubleFaultRate	Displayed serve rates when available.
firstServeIn / firstServeWon / secondServeWon	Displayed first- and second-serve percentages.
breakPointsSaved	Displayed break-point statistic.
matchDuration	Displayed match duration when available.
sourceUrl	Public player page used for the exported row.

Who is it for?

This Actor is useful for tennis analysts, sports researchers, journalists, fantasy and scouting workflows, and developers building player-history datasets. It is designed for public recent-match data for a specific player, not live scoring or private account data.

Tips

• Copy the exact player slug from the public player URL to avoid targeting a similarly named player.
• Begin with a small maxItems value when testing a new workflow.
• Use sourceUrl to retain a direct public reference alongside every exported row.
• Export to CSV or Excel for spreadsheets, or consume the default dataset from your application.

Pricing and limits

View current pricing on the Actor’s Pricing tab. A small run-start fee applies, followed by a charge for each exported match result. The tier shown on the Pricing tab is authoritative.

The Actor exports rows currently available on the public player page. It does not invent missing statistics, historical rows that are no longer present, or live match updates.

API usage

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/tennis-abstract-scraper').call({
  playerSlug: 'NovakDjokovic',
  maxItems: 20,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("fetch_cat/tennis-abstract-scraper").call(
    run_input={"playerSlug": "NovakDjokovic", "maxItems": 20}
)
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

cURL

curl -X POST \
  'https://api.apify.com/v2/acts/fetch_cat~tennis-abstract-scraper/runs?token=<APIFY_TOKEN>' \
  -H 'content-type: application/json' \
  -d '{"playerSlug":"NovakDjokovic","maxItems":20}'

MCP and AI agents

Use this Actor from Apify MCP by enabling https://mcp.apify.com?tools=fetch_cat/tennis-abstract-scraper.

For Claude Code, add the MCP server:

$claude mcp add apify -- npx -y @apify/mcp-server --tools=fetch_cat/tennis-abstract-scraper

Or add this server configuration:

{
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": ["-y", "@apify/mcp-server", "--tools=fetch_cat/tennis-abstract-scraper"],
      "env": { "APIFY_TOKEN": "<APIFY_TOKEN>" }
    }
  }
}

Example prompts: “Export the latest 20 matches for NovakDjokovic” or “Return IgaSwiatek’s recent hard-court matches as a table.”

Related Actors

Extend player research with these FetchCat Actors:

• Google Search Results Scraper for tournament and news discovery.
• YouTube Channel Videos Scraper for public player-channel video catalogs.
• YouTube Comments Scraper for public audience discussion research.
• Instagram Profile & Posts Scraper for public player social-content exports.
• Website Content Crawler for tournament or federation web pages.

This Actor focuses specifically on recent player match rows from Tennis Abstract.

FAQ

Do I need a Tennis Abstract account?

No. The Actor uses public player information and does not require login credentials.

Why can a statistic be null?

A null value means that statistic was not displayed for that public match row. The Actor preserves the source’s availability rather than estimating data.

Can I request more than 200 matches?

The current maximum is 200 rows per run. Split research into player-specific runs to keep exports focused and manageable.

Is this live match data?

No. It exports recent match rows available on the public player page at run time.

Support

Open an issue on the Actor page with the player slug and a non-sensitive example. Include the expected public player page so support can reproduce the request.