Tennis Abstract Player Match Scraper avatar

Tennis Abstract Player Match Scraper

Pricing

from $3.59 / 1,000 match results

Go to Apify Store
Tennis Abstract Player Match Scraper

Tennis Abstract Player Match Scraper

Export public recent match results and match statistics for a Tennis Abstract player.

Pricing

from $3.59 / 1,000 match results

Rating

0.0

(0)

Developer

Fetch Cat

Fetch Cat

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

9 days ago

Last modified

Categories

Features

Limited permissions

Share

The Tennis Abstract Player Match Scraper exports recent public player match results and, optionally, the player's listed tour-level finals into JSON, CSV or Excel. Get opponents, scores, tournament context, rankings and available serve statistics for one player. Filter by surface, result, opponent or date. This is not a guaranteed full career history or a live score service.

Quick start

  1. Copy the player identifier from a Tennis Abstract player URL. For a URL ending in ?p=IgaSwiatek, use IgaSwiatek.
  2. Enter the slug and choose a small match limit.
  3. Run the Actor and open its dataset.
{"playerSlug":"NovakDjokovic","maxItems":20}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose an example to start with a small, preconfigured input.

What you get

  • One row per match, up to your requested limit; recent matches by default.
  • Optional export of the player's listed tour-level career finals, deduplicated against recent matches.
  • Surface, result, opponent and date filters applied before the match limit.
  • Tournament, surface, round, opponent and score fields, plus seeds, entry status and match status when available.
  • Rankings, serve percentages and match duration when shown.
  • Source links for checking each export against the public data.

Who is it for?

For tennis analysts, sports researchers, journalists and developers building tennis player match history datasets. Use the returned tennis match statistics in spreadsheets, dashboards or analytical workflows.

Input settings

InputDescription
playerSlugRequired player identifier, such as NovakDjokovic.
maxItemsMaximum matching rows, from 1 to 200, including finals when enabled. Defaults to 20.
surfacesOptional: keep only Hard, Clay, Grass and/or Carpet matches.
matchResultOptional: all (default), win or loss.
opponentOptional: part of an opponent's name (for example Alcaraz) or their slug (CarlosAlcaraz).
dateFrom, dateToOptional date window in YYYY-MM-DD format.
includeFinalsAlso export the player's listed tour-level finals, marked section: "final". Off by default.

Filters are applied before maxItems. If no available match fits your filters, the run finishes successfully with no results and a message explaining why.

For example, this input exports the player's clay-court losses since 2025, including finals:

{
"playerSlug": "NovakDjokovic",
"surfaces": ["Clay"],
"matchResult": "loss",
"dateFrom": "2025-01-01",
"includeFinals": true,
"maxItems": 50
}

The scraper uses public data without login. There is no connection selector or supported proxy input.

Output data

Each dataset row describes a match. The following is a shape-only illustration, not an observed match result:

{
"playerSlug": "ExamplePlayer",
"playerName": "Example Player",
"date": "source date text",
"tournament": "source tournament name",
"surface": "Hard",
"round": "source round",
"opponent": "source opponent name",
"result": "unknown",
"score": "source score text",
"section": "recent",
"dateIso": "2026-01-01",
"tournamentId": "2026-0000",
"playerSeed": "10",
"opponentSeed": "Q",
"breakPointsSavedCount": 4,
"breakPointsFaced": 7,
"matchMinutes": 134,
"matchStatus": "completed",
"sourceUrl": "http://www.tennisabstract.com/jsfrags/ExamplePlayer.js"
}
FieldsMeaning
playerSlug, playerNameRequested identifier and a display name derived from that identifier.
date, tournament, tournamentUrlSource date text, tournament name and available link.
surface, roundSurface and tournament round.
playerRank, opponentRankNumeric source rankings when available.
opponent, opponentSlug, opponentCountryOpponent identity and available source metadata.
result, scorewin, loss or unknown, and source score text.
dominanceRatioNumeric dominance ratio when available.
aceRate, doubleFaultRateSource-provided serve rates.
firstServeIn, firstServeWon, secondServeWonSource-provided serve statistics.
breakPointsSaved, matchDurationAvailable break-point statistic and match duration.
sourceUrlPublic source reference.
sectionrecent for the latest matches, final for a listed career final.
dateIso, tournamentIdDate as YYYY-MM-DD and the Tennis Abstract tournament ID.
playerSeed, opponentSeedSeed number or entry code (Q, WC, LL, SE, PR) when listed.
breakPointsSavedCount, breakPointsFacedBreak points saved and faced, as numbers.
matchMinutesMatch duration in minutes.
matchStatuscompleted, retired, walkover or defaulted, read from the score.

Dates and percentage statistics retain source text. Optional values may be null. Do not assume every match includes every statistic.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

This Actor uses pay-per-event pricing. The start event is charged when extraction starts, including runs that return no matches.

The result event is charged when a match is prepared for export. A later storage failure can prevent that row from appearing in the dataset. Lower maxItems to bound the number of match export attempts.

See the live Pricing tab for current rates and discounts.

Tips for best results

  • Use the exact player slug. Copy it from the public player URL to avoid a similarly named player. A slug with no Tennis Abstract page finishes with no results and a status message saying so.
  • Max cost and timeout. If your run reaches its max cost or timeout, it stops cleanly and keeps the matches already saved.
  • Start with a small limit. Check the returned rows before increasing maxItems.
  • Keep source references. Use sourceUrl to check unexpected values.
  • Filter before export. Use the surface, result, opponent and date filters to export only the matches you need. If none match, the run finishes with an explanatory message and no per-result charges; the start charge still applies.

Limits and caveats

The Actor exports recent matches and, optionally, the player's listed tour-level finals currently available for one public player. It does not supply live scores, private account data or a guaranteed full career history.

Tennis Abstract can change or restrict its public data. Missing statistics are not estimated. An available results table with no matches can return an empty dataset. Access failures or an unexpected source format can fail the run.

Some records may be missing if an individual save fails or the run reaches its time limit. Inspect the dataset and run summary before treating an export as complete. This is an independent tool, not an official Tennis Abstract API.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~tennis-abstract-scraper/runs' \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"playerSlug":"NovakDjokovic","maxItems":20}'

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

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ["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)

MCP and AI agents

You can ask your AI assistant to collect data with Tennis Abstract Player Match Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Tennis Abstract Player Match Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com?tools=fetch_cat/tennis-abstract-scraper"
}
}
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Tennis Abstract Player Match Scraper by Fetch Cat, or give it the identifier fetch_cat/tennis-abstract-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

  • “Get Novak Djokovic’s latest 20 available matches and make a table of opponents and scores.”
  • “Collect Iga Swiatek’s recent 20 matches, then compare her results by surface.”
  • “Export Rafael Nadal’s latest 10 available matches and summarize the serve statistics that are present.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

How can I export a Tennis Abstract player match history?

Enter the exact public player slug and run the Actor. Download the dataset or read it through the API. The export includes recent matches and, optionally, the player's listed tour-level finals available from the source. Set includeFinals to true to include finals; this is not a guaranteed full career history.

Which serve statistics are included?

Available fields include ace and double-fault rates, first-serve percentages, second-serve points won and break points saved. Availability varies by match.

Do I need a Tennis Abstract account?

No. The scraper uses public data and has no login input.

Can I request more than 200 matches?

No. The maximum is 200 per run, and the source may offer fewer rows. Repeating the same request does not reveal older unavailable matches.

Can an AI assistant use this scraper?

Use Apify’s hosted MCP setup above or call the API. The assistant can analyze the returned data, but the scraper itself does not summarize matches.

Where do I find the current price?

Use the Actor’s live Pricing tab. Both the start event and attempted match exports can incur charges.

Is this an official API or a live score service?

Neither. Use Tennis Abstract’s public site for manual research or a dedicated licensed sports feed when you need live scoring.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥