Export Two Rivals' Match Logs for H2H Analysis

A rivalry is two match logs joined on opponent — pull both sides. Thirdwatch's Tennis Abstract Scraper returns any ATP or WTA player's full match log — surface, round, opponent, score, and the deep serve/return stats that make Tennis Abstract the analyst's source.

Skip the setup: Run this as a ready-to-go task on Apify — pre-loaded with the configuration from this guide.

Why export a rivalry

Head-to-head pages show wins and losses; the interesting analysis — how the matchup evolved on which surfaces — needs both players' full logs.

Two names in players return both logs; the H2H matches are the intersection on opponent.

The scraper reads the site's per-player match-log data directly, so a player name in means the complete history out.

How does this compare to the alternatives?

Why this Actor

• Full match logs per player — the complete career arc, not just recent form.
• Deep stats per match: serve/return points, aces, double faults, break points.
• ATP and WTA coverage — any player name resolves.
• Context fields on every row: tournament, surface, round, both rankings.
• Player names or slugs — no ID lookup needed.

How to do it in 3 steps

Step 1: Configure the input

Set the inputs as shown below — players takes the targets, player names or slugs; maxMatches bounds how far back each player's log goes.

Step 2: Run the Actor

Run it from the console, the API, or the linked saved task. One dataset row is written per match.

Step 3: Use the output

Each row carries the match context — date, tournament, surface, round, opponent, score, rankings — plus the serve and return stat columns Tennis Abstract publishes.

{
  "players": [
    "Novak Djokovic",
    "Rafael Nadal"
  ],
  "maxMatches": 30
}

Each dataset row looks like:

{
  "player": "Novak Djokovic",
  "playerSlug": "NovakDjokovic",
  "date": "2026-07-13",
  "tournament": "Wimbledon",
  "surface": "Grass",
  "round": "F",
  "opponent": "Jannik Sinner",
  "score": "6-4 3-6 7-6 6-3",
  "rank": "3",
  "opp_rank": "1",
  "serve_pts": "74/102",
  "aces": "9"
}

What to watch for

Coverage follows Tennis Abstract's own archive — exhibitions and some lower-tier events are absent. A few unusual table columns may appear as colN on older rows.

Related use cases

• Pull a Player's Complete Tennis Abstract Match Log
• Scan Current Form Across Several Top Players
• Build Surface-Split Stats from a Player's Match Log
• Pull a WTA Player's Season Match Log
• All Thirdwatch use-case guides

Run the Tennis Abstract Scraper on Apify Store — pay per result, free to try, no credit card to test.