Tennis Matches + Odds, Form & Head-to-Head [$0.02/match] avatar

Tennis Matches + Odds, Form & Head-to-Head [$0.02/match]

Pricing

from $20.00 / 1,000 match with odds, form and head-to-heads

Go to Apify Store
Tennis Matches + Odds, Form & Head-to-Head [$0.02/match]

Tennis Matches + Odds, Form & Head-to-Head [$0.02/match]

ATP and WTA matches for any day, live or finished, with 15+ bookmakers' opening and current odds, rankings, last-10 form, surface record, and head-to-head in one JSON row per match. Filter by tour, tournament, player. Built for betting models and AI agents. $0.02 per enriched match.

Pricing

from $20.00 / 1,000 match with odds, form and head-to-heads

Rating

0.0

(0)

Developer

Perch Data

Perch Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

17 hours ago

Last modified

Categories

Share

Tennis Matches + Odds, Form & Head-to-Head (ATP/WTA)

One JSON row per tennis match with everything a betting model or an AI agent asks for before it prices a match, in a single call:

  • The match: date, start time in UTC, tournament, tour (ATP/WTA), round, surface, both players with seeds, status (scheduled, in progress, finished), and the score with tiebreaks.
  • Odds: the site's reference odds on the list, plus, when enriched, 15+ bookmakers' current and opening odds per player, the trend since opening, the best available price and who offers it, and optionally the full timestamped movement history.
  • Form: each player's last N matches (opponent, round, date, score, won/lost), a W/L sequence like WWLWW, the current streak, and this year's win/loss record by surface.
  • Head-to-head: the total and every previous meeting with year, tournament, surface, round, and score.
  • Rankings and bio: singles rank, birthdate, height, weight, handedness.

Other tennis actors on the store sell one of those pieces each. This one joins them so an agent does not need four actors and a merge step.

Source: TennisExplorer, public pages, no login. Coverage is ATP, WTA, Challenger, ITF, and UTR events. Nothing is guessed; missing values are null.

Quick start

Today's ATP singles with odds, form, and head-to-head:

{ "tour": "atp" }

Every match at a tournament over the next three days, plain rows only (cheapest):

{ "tournament": "US Open", "days": 3, "enrich": false, "maxMatches": 500 }

Yesterday's finished WTA results with closing odds and the score:

{ "mode": "results", "date": "2026-09-08", "tour": "wta", "enrich": false }

Everything in progress right now, with current set scores and live bookmaker prices:

{ "mode": "live" }

One player's next match with the full odds movement from every bookmaker:

{ "player": "Alcaraz", "days": 7, "status": "scheduled", "oddsHistory": true, "maxMatches": 1 }

Input

FieldTypeNotes
modeschedule | results | liveSchedule lists upcoming, live, and completed matches of the day. Results lists finished matches only. Live lists matches in progress right now with the current set scores, a snapshot as of fetched_at_utc; it ignores date and days. Default schedule.
dateYYYY-MM-DDDefaults to today. The site's day runs on Central European time.
days1 to 14Consecutive days starting at date. Default 1.
tourall | atp | wtaDefault all.
doublesbooleanDoubles instead of singles. Default false.
tournamentstringCase-insensitive substring of the tournament name.
playerstringCase-insensitive substring of either player's name.
statusscheduled | in_progress | finishedKeep only one state.
maxMatchesintegerStop after this many. Default 50.
enrichbooleanFetch each match's detail page. Default true. One request per match, about a second each.
latestMatches1 to 30Recent matches per player when enriching. Default 10.
oddsHistorybooleanInclude every recorded odds change per bookmaker. Default false.
previewbooleanAdd a written preview to each enriched row (below). Default false. Charged as match-preview on top of enriched-match.
requestDelaySecondsnumberPoliteness delay toward the source. Default 0.4.

Output

Every row has these top-level fields:

FieldMeaning
match_id, match_urlSource identifiers.
date, time_site, start_utcCalendar day and start time as listed (Central European time) and converted to UTC.
fetched_at_utcWhen this row was read from the source. Age a live or odds snapshot with it.
statusscheduled, in_progress, or finished.
tournamentname, url, slug, year, tour (atp/wta), format (singles/doubles).
round, surfaceFrom the detail page (enriched rows only).
home, awayname, slug, url, seed. "Home" is the first-listed player.
oddsReference odds from the list page: home, away (decimal).
h2h_listHead-to-head count as shown on the schedule list, when present.
resultwinner (home/away), sets_home, sets_away, sets[] with home, away, tiebreak_loser_points, and score like 5-7, 3-6, 7-5, 6-3, 7-6(6).
result_noteretired_or_walkover when a finished match ended short.

With enrich (default), the enrichment block adds:

FieldMeaning
statusok, partial (page found but no odds and no recent matches), parse_failed, fetch_failed. Only ok and partial rows are charged as enriched.
home, awayfull_name, singles_rank, birthdate, height, weight, plays, turned_pro, surface_record (this year's {wins, losses} per surface), form (played, wins, losses, streak like 4W, sequence like WWWWL), latest_matches[] (date, tournament, round, round_full, opponent, won, sets, score, match_id).
h2hhome_wins, away_wins, matches[] with year, tournament, surface, round, winner_name, loser_name, score, match_id.
bookmakers[]Per bookmaker: home, away (current decimal odds), home_opening, away_opening, home_trend, away_trend (up/down), and with oddsHistory the home_history[]/away_history[] of {at_site, odds, change}.
bookmaker_count, best_oddsHow many books priced the match, and the highest home/away price with the bookmaker offering it.
marketDerived from every bookmaker that priced both sides: consensus_home/consensus_away (mean odds), fair_prob_home/fair_prob_away (implied probabilities with the margin removed), overround, favorite, opening_consensus_*, opening_fair_prob_home, and prob_shift_home (how far the fair probability moved since opening; negative means the market turned against the first player).
final_scoreFor finished matches, the detail page's own score line, e.g. 2 : 1 (4-6, 6-4, 7-6(8)).
home.partner, away.partnerDoubles only: the second player of each pair. Rankings and bio describe the first-listed player.

With preview: true, each enriched row also carries:

FieldMeaning
preview{text, model, generated_at}: 90 to 140 words written by Claude from the row's own numbers: what the market prices and how it moved, then which of the form, surface, ranking, and head-to-head facts support or cut against that price. It names no winner and recommends nothing; a null field in the row is reported as missing, never guessed. null when the model could not produce one (that row is not charged the preview event). Absent when preview is off or the budget ran out.

Pricing

Pay per event. Free-tier credit covers a few hundred matches.

EventPriceWhen
enriched-match$0.02A match row with the enrichment block (odds, form, head-to-head).
match$0.002A plain match row (enrich: false, or the budget ran out).
match-preview$0.10An enriched row that also carries a written preview. Charged in addition to enriched-match, only for rows where preview is not null.

If maxTotalChargeUsd is set, the actor works out up front how many matches it can enrich within the budget, enriches those, and returns the rest plain; previews are capped the same way after enrichment. A run is never charged for rows it did not return. Failed enrichment (site error, layout change) is returned plain and charged as match.

Use it from Zapier or Clay

No code needed; both call the actor with your own Apify account and you pay the per-row prices above. In Zapier, a Schedule trigger each morning, the Apify action Run Actor (synchronous) with { "mode": "schedule", "tour": "atp", "enrich": true, "maxMatches": 30 }, then Fetch Dataset Items into a Google Sheet, a Slack channel, or a Notion database gives you the day's card with odds and form before play starts. In Clay, Import data from Apify Actor with the same input fills a table with one match per row.

Wrap this in an afternoon

Reselling these rows behind your own search box is allowed and expected; it is what the per-row price is for. A zero-dependency starter kit does it: a one-page storefront, Stripe credit packs that never expire (no subscription), and one call to this actor per search. Point it at perchpermits/tennis-matches-odds-form, set your price per row, and deploy anywhere Node runs. Source and setup: wrapper-kit. At $0.02 an enriched row here, a $0.10 charge per row on your side leaves about 80% before Stripe's fee.

Limits and honesty

  • Times are converted from Central European time to UTC. If the source changes its display timezone the start_utc values shift; time_site is always the raw value.
  • Live scores are set-level snapshots at run time, not a point-by-point stream. Run again for an update; fetched_at_utc tells you how old a row is.
  • If every enrichment in a run fails, the run fails and nothing is charged, so a blocked or changed source never turns into silent plain rows at the enriched price.
  • The source does not publish match statistics (aces, serve percentages) on these pages, so none are returned.
  • Odds are the bookmakers' listed prices at the time the source recorded them; they are for information, not a betting instruction. Check your local law before acting on them.
  • If the source changes its layout the run fails loudly with Source drift detected and nothing is charged, rather than returning empty rows.

Support

Open an issue on the actor page. Layout changes at the source are fixed within days.