Every Tennis API v2 REST Endpoint, Explained
A practical guide to all 102 documented REST routes for fixtures, players, head-to-head data, rankings, tournaments, predictions, potential fixtures, live scores, odds and supporting metadata—with a direct documentation link for every endpoint.
Last reviewed against the public v2 documentation: 24 August 2026.
curl --request GET \
--url 'https://tennis-api-atp-wta-itf.p.rapidapi.com/tennis/v2/atp/fixtures' \
--header 'X-RapidAPI-Key: YOUR_KEY' \
--header 'X-RapidAPI-Host: tennis-api-atp-wta-itf.p.rapidapi.com'
// JSON response
{
"data": [{ "player1": "…", "player2": "…" }],
"hasNextPage": false
}
How Tennis API requests work
Every request combines the host for your RapidAPI product with a common v2 path. The flagship host can serve core, advanced, prediction, live and odds routes.
https://{host}/tennis/v2/{feature-specific-path}Live and odds pattern:
https://{host}/tennis/v2/extend/api/{feature-specific-path}
ATP, WTA and ITF coverage
The {tour_type} path value accepts atp or wta. ITF-level events are included within those datasets; itf is not a valid tour-type value.
Preserve legacy spellings
Two documented routes contain historical spellings: intersting-h2h and past-champtions. Copy them exactly unless the documentation is updated.
Choose the correct RapidAPI host
IMPORTANT
We offer several Tennis API products, but we strongly recommend subscribing only to our flagship product, which includes everything we offer.
Our top-level plan, Tennis API – ATP WTA ITF, provides access to all available data and endpoints. There is no need to subscribe to any of our smaller, content-specific products, as they are already included in this plan.
You can view the Tennis API – ATP WTA ITF product here: Tennis API – ATP WTA ITF
Already subscribed to a sub-product?
No problem. The endpoints are the same, but the base URL is different depending on which RapidAPI product you're subscribed to.
Paths stay broadly consistent across products, but the host and supported feature set depend on the subscription you purchased.
| Product | Host | Path prefix | Best for |
|---|---|---|---|
| Tennis API – ATP WTA ITF | tennis-api-atp-wta-itf.p.rapidapi.com | /tennis/v2//tennis/v2/extend/api/ | Complete flagship access |
| Tennis Stats API | tennis-stats-api.p.rapidapi.com | /tennis/v2/ | H2H and advanced statistics |
| Tennis Predictions API | tennis-predictions-api.p.rapidapi.com | /tennis/v2/ | Predictions and probabilities |
| Tennis Live API | tennis-live-api.p.rapidapi.com | /tennis/v2/extend/api/ | Live events, scores and odds |
Use the same host in the request URL and the X-RapidAPI-Host header. A mismatched host can cause a 403 response even when the API key is valid.
A safe first request
Keep the API key on your server. The example below deliberately uses a placeholder and can be adapted for a backend route, serverless function or scheduled data job.
curl --request GET \
--url 'https://tennis-api-atp-wta-itf.p.rapidapi.com/tennis/v2/atp/fixtures?include=round,tournament.court' \
--header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY' \
--header 'X-RapidAPI-Host: tennis-api-atp-wta-itf.p.rapidapi.com'The public documentation describes a server-side throttle of 100 requests per minute per IP, in addition to any RapidAPI quota attached to your plan.
200Success400Invalid input401Missing/invalid key403Host or plan restriction404Resource not found429Rate limit exceeded
Which endpoint family should you use?
Start with the family that matches the page or feature you are building, then combine related routes to enrich the result.
| Endpoint family | Routes | What it covers |
|---|---|---|
| Fixtures API | 6 | Build match schedules, date-based calendars, tournament pages, player schedules and historical matchup views. Upcoming fixtures are separate from the completed-match archive. |
| Players API | 23 | Create player pages and analytical tools with profiles, ranking snapshots, titles, finals, match history, surface records, statistics, status and filter metadata. |
| Head-to-Head API | 22 | Compare any two players—or one player against the field—using rivalry records, match lists, surface splits, serve and return metrics, recent form and potential matchups. |
| Rankings API | 7 | Retrieve current singles and doubles rankings, year-to-date races, Top 10 lists, historical ranking snapshots and complete date-specific ranking tables. |
| Tournaments API | 13 | Power event calendars, tournament landing pages, year-by-year history, draws, seed lists, points tables, champions and historical results. |
| Upcoming Matches & Predictions | 6 | Discover upcoming ATP and WTA matches, surface and tournament filters, priority matches and model-driven prediction output. |
| Potential Fixtures API | 4 | Expose matchups that can still occur based on active tournament draws—useful for bracket scenarios, editorial planning and possible-opponent tools. |
| Live Events & Odds API | 15 | Use the extended API prefix for live-event discovery, current score state, event timelines, point-by-point data, bookmakers, markets and odds analytics. |
| Reference & Search Endpoints | 6 | Retrieve the IDs and labels used across the API, and search players and tournaments. Stable lookup tables are good candidates for application-level caching. |
What the data can look like in a product
These are semantic HTML tables—not tiny SVG screenshots—so they remain readable, scrollable and accessible on mobile. All values are illustrative.
| Date / time | Tour | Tournament | Round | Player 1 | Player 2 | Status |
|---|---|---|---|---|---|---|
| 26 Aug · 14:00 | ATP | Example Masters | Quarter-final | Sample Player A | Sample Player B | Upcoming |
| 26 Aug · 16:30 | WTA | Example WTA 1000 | Round of 16 | Sample Player C | Sample Player D | Upcoming |
| 26 Aug · 19:00 | ATP | Example ATP 500 | Semi-final | Sample Player E | Sample Player F | Upcoming |
| Surface | Wins | Losses | Win rate | Titles | Recent form |
|---|---|---|---|---|---|
| Hard | 42 | 11 | 79.2% | 4 | W · W · L · W · W |
| Clay | 26 | 8 | 76.5% | 2 | W · L · W · W · W |
| Grass | 12 | 3 | 80.0% | 1 | W · W · W · L · W |
| Category | Sample Player A | Sample Player B | Leader |
|---|---|---|---|
| Overall meetings | 8 wins | 6 wins | Player A |
| Hard courts | 5 | 4 | Player A |
| Clay courts | 2 | 2 | Tied |
| Grass courts | 1 | 0 | Player A |
| Break points won | 41% | 38% | Player A |
| Rank | Player | Country | Points | Weekly movement | Ranking date |
|---|---|---|---|---|---|
| 1 | Sample Player A | ESP | 10,250 | +1 | 24 Aug 2026 |
| 2 | Sample Player B | ITA | 9,860 | −1 | 24 Aug 2026 |
| 3 | Sample Player C | USA | 7,440 | 0 | 24 Aug 2026 |
| Seed | Player | Country | Entry rank | Draw section | Status |
|---|---|---|---|---|---|
| 1 | Sample Player A | ESP | 2 | Top half | Active |
| 2 | Sample Player B | ITA | 4 | Bottom half | Active |
| 3 | Sample Player C | USA | 7 | Bottom half | Scheduled |
| Status | Match | Set score | Current points | Market | Best player 1 odds | Best player 2 odds |
|---|---|---|---|---|---|---|
| In play | Sample Player A vs Sample Player B | 6–4, 2–3 | 30–15 | Match winner | 1.72 | 2.18 |
All 102 documented REST endpoints
Search by route, data type or use case. Endpoint families are collapsible, and every route links directly to its documentation section.
Showing all 102 endpoint routes.
/tennis/v2/
LIVE PREFIXUses /tennis/v2/extend/api/
ULTRA / MEGAOdds or prediction access noted in current docs
Badges identify the documented path family or an explicit plan restriction; confirm current access against your RapidAPI subscription.
01 6 documented routesFixtures APIBuild match schedules, date-based calendars, tournament pages, player schedules and historical matchup views. Upcoming fixtures are separate from the completed-match archive. Explore endpoints
Open any route for fields, inputs, use cases and a direct documentation link.
Module documentation ↗
GETToday's fixtures
/tennis/v2/{tour_type}/fixtures
CORE PREFIX
Returns today's upcoming ATP or WTA matches, with optional tournament, surface, country, H2H and round relationships.
Open this endpoint in the documentation (opens in a new tab)
GETFixtures by date
/tennis/v2/{tour_type}/fixtures/{date_only}
CORE PREFIX
Returns all fixtures scheduled for one date in YYYY-MM-DD format.
Open this endpoint in the documentation (opens in a new tab)
GETFixtures by date range
/tennis/v2/{tour_type}/fixtures/{start_date_range}/{end_date_range}
CORE PREFIX
Returns fixtures across an inclusive date window, ideal for weekly schedules and event calendars.
Open this endpoint in the documentation (opens in a new tab)
GETFixtures by tournament
/tennis/v2/{tour_type}/fixtures/tournament/{tournament_id}
CORE PREFIX
Retrieves upcoming fixtures belonging to a specific tournament season.
Open this endpoint in the documentation (opens in a new tab)
GETFixtures by player
/tennis/v2/{tour_type}/fixtures/player/{player_id}
CORE PREFIX
Returns upcoming fixtures involving one player.
Open this endpoint in the documentation (opens in a new tab)
GETHistorical fixtures between two players
/tennis/v2/{tour_type}/fixtures/h2h/{player1_id}/{player2_id}
CORE PREFIX
Returns historical meetings for two players using the archived match dataset.
Open this endpoint in the documentation (opens in a new tab)02 23 documented routesPlayers APICreate player pages and analytical tools with profiles, ranking snapshots, titles, finals, match history, surface records, statistics, status and filter metadata. Explore endpoints
Open any route for fields, inputs, use cases and a direct documentation link.
Module documentation ↗
GETAll players
/tennis/v2/{tour_type}/player
CORE PREFIX
Paginated ATP or WTA player list with ranking snapshot and optional country data.
Open this endpoint in the documentation (opens in a new tab)
GETPlayer profile
/tennis/v2/{tour_type}/player/profile/{player_id}
CORE PREFIX
Full profile details with optional recent form, ranking history and country object.
Open this endpoint in the documentation (opens in a new tab)
GETPlayer titles
/tennis/v2/{tour_type}/player/titles/{player_id}
CORE PREFIX
All tournament titles won by the selected player.
Open this endpoint in the documentation (opens in a new tab)
GETPlayer match statistics
/tennis/v2/{tour_type}/player/match-stats/{player_id}
CORE PREFIX
Aggregated records such as wins/losses, aces and break-point performance.
Open this endpoint in the documentation (opens in a new tab)
GETPlayer past matches
/tennis/v2/{tour_type}/player/past-matches/{player_id}
CORE PREFIX
Completed results, most recent first, with filters for year, round, court, event and tournament tier.
Open this endpoint in the documentation (opens in a new tab)
GETSurface summary
/tennis/v2/{tour_type}/player/surface-summary/{player_id}
CORE PREFIX
Win/loss records by hard, clay, grass, carpet and indoor-hard surfaces.
Open this endpoint in the documentation (opens in a new tab)
GETPerformance breakdown
/tennis/v2/{tour_type}/player/perf-breakdown/{player_id}
CORE PREFIX
Granular serve, return, pressure and situational performance metrics where available.
Open this endpoint in the documentation (opens in a new tab)
GETPlayer finals
/tennis/v2/{tour_type}/player/finals/{player_id}
CORE PREFIX
Finals reached, including both wins and losses, with optional historical filters.
Open this endpoint in the documentation (opens in a new tab)
GETInteresting H2H
/tennis/v2/{tour_type}/player/intersting-h2h/{player_id}
CORE PREFIX
Notable rivalries and opponent records for a player.
GETPlayer filter metadata
/tennis/v2/{tour_type}/player/filter/{player_id}
CORE PREFIX
Available filter categories for building data-driven player analysis UIs.
Open this endpoint in the documentation (opens in a new tab)
GETTournament record
/tennis/v2/{tour_type}/player/tournament-record/{player_id}/{tourId}
CORE PREFIX
A player's year-by-year career record at one tournament family.
Open this endpoint in the documentation (opens in a new tab)
GETRich profile by name or ID
/tennis/v2/profile/{player_id_or_name}
CORE PREFIX
Rich biographical and career profile, including ranking, prize money, coach, playing style and profile images.
Open this endpoint in the documentation (opens in a new tab)
GETCareer statistics
/tennis/v2/profile/{player_id_or_name}/statistics
CORE PREFIX
Career-level performance, rankings, tournament categories, recent results, titles and finals.
Open this endpoint in the documentation (opens in a new tab)
GETProfile surface summary
/tennis/v2/profile/{player_id_or_name}/surface-summary
CORE PREFIX
Year-by-year records across hard, indoor hard, clay and grass.
Open this endpoint in the documentation (opens in a new tab)
GETMatches played
/tennis/v2/profile/{player_id_or_name}/matches-played
CORE PREFIX
Paginated match history with opponent, score, tournament and round, filterable by surface and year.
Open this endpoint in the documentation (opens in a new tab)
GETFinals by year
/tennis/v2/profile/{player_id_or_name}/finals/{year}
CORE PREFIX
All tournament finals reached during one season, including result.
Open this endpoint in the documentation (opens in a new tab)
GETMatch stats by year
/tennis/v2/profile/{player_id_or_name}/match-stat/{year}
CORE PREFIX
Season-specific serve, return, break-point, game and points statistics.
Open this endpoint in the documentation (opens in a new tab)
GETPlayer status
/tennis/v2/profile/{player_id_or_name}/player-status
CORE PREFIX
Returns the player’s current status, such as active or inactive.
Open this endpoint in the documentation (opens in a new tab)
GETPerformance breakdown
/tennis/v2/profile/{player_id_or_name}/breakdown
CORE PREFIX
Win/loss performance segmented by round, tournament level and opponent-ranking range.
Open this endpoint in the documentation (opens in a new tab)
GETInteresting rivalries
/tennis/v2/profile/{player_id_or_name}/interesting
CORE PREFIX
Notable opponent relationships with overall H2H records and profile context.
Open this endpoint in the documentation (opens in a new tab)
GETProfile filter values
/tennis/v2/profile/{player_id_or_name}/filters
CORE PREFIX
Returns the surfaces, rounds, tournament levels, tournaments and seasons available for profile-statistics filters.
Open this endpoint in the documentation (opens in a new tab)
GETPlayer search
/tennis/v2/profile/search/{name}/{tour_type}
CORE PREFIX
Search players by name within ATP or WTA.
Open this endpoint in the documentation (opens in a new tab)
GETNext match
/tennis/v2/profile/{player_id_or_name}/upcoming
CORE PREFIX
Returns the player's next scheduled match when one is available.
Open this endpoint in the documentation (opens in a new tab)03 22 documented routesHead-to-Head APICompare any two players—or one player against the field—using rivalry records, match lists, surface splits, serve and return metrics, recent form and potential matchups. Explore endpoints
Open any route for fields, inputs, use cases and a direct documentation link.
Module documentation ↗
GETH2H info
/tennis/v2/{tour_type}/h2h/info/{player1_id}/{player2_id}
CORE PREFIX
Head-to-head win counts broken down by surface.
Open this endpoint in the documentation (opens in a new tab)
GETH2H matches
/tennis/v2/{tour_type}/h2h/matches/{player1_id}/{player2_id}
CORE PREFIX
Full meeting history with scores and tournament details.
Open this endpoint in the documentation (opens in a new tab)
GETAggregated H2H stats
/tennis/v2/{tour_type}/h2h/stats/{player1_id}/{player2_id}
CORE PREFIX
Combined serve and return comparison across meetings, optionally filtered by surface.
Open this endpoint in the documentation (opens in a new tab)
GETH2H filters
/tennis/v2/{tour_type}/h2h/filter/{player1_id}/{player2_id}
CORE PREFIX
Available surfaces, years, rounds, tournaments and tier values in a rivalry.
Open this endpoint in the documentation (opens in a new tab)
GETVs all opponents
/tennis/v2/{tour_type}/h2h/vs-all-stats/{player_id}
CORE PREFIX
A player's record and stats against every opponent faced.
Open this endpoint in the documentation (opens in a new tab)
GETMatch stats in tournament
/tennis/v2/{tour_type}/h2h/match-stats/{tournament_id}/{player1_id}/{player2_id}
CORE PREFIX
Detailed statistics from a specific encounter at a particular tournament.
Open this endpoint in the documentation (opens in a new tab)
GETPlayer tour type
/tennis/v2/h2h/playerType/{player_id_or_name}
CORE PREFIX
Identifies whether a player belongs to ATP or WTA.
Open this endpoint in the documentation (opens in a new tab)
GETRich H2H profile
/tennis/v2/h2h/profile/{tour_type}/{player1_id_or_name}/{player2_id_or_name}/{limit}
CORE PREFIX
Comprehensive matchup profile with rankings, form, careers, titles and surface H2H.
/tennis/v2/h2h/{tour_type}/{player1_id_or_name}/{player2_id_or_name}/{limit}
GETSurface breakdown
/tennis/v2/h2h/surfaceBreakdown/{tour_type}/{player_id_or_name}
CORE PREFIX
Surface-level win/loss breakdown for matchup analysis.
Open this endpoint in the documentation (opens in a new tab)
GETAdvanced H2H statistics
/tennis/v2/h2h/stats/{tour_type}/{player1_id_or_name}/{player2_id_or_name}
CORE PREFIX
Rich serving, returning, tiebreak, deciding-set and surface statistics with year/surface/tournament filters.
Open this endpoint in the documentation (opens in a new tab)
GETAdvanced H2H filters
/tennis/v2/h2h/filters/{player1_id_or_name}/{player2_id_or_name}/{tour_type}
CORE PREFIX
Filter metadata for surfaces, rounds, levels, tournaments and seasons.
Open this endpoint in the documentation (opens in a new tab)
GETUpcoming H2H event
/tennis/v2/h2h/upcoming/{tour_type}/{player1_id_or_name}/{player2_id_or_name}
CORE PREFIX
The next scheduled meeting between two players, including event and court context.
Open this endpoint in the documentation (opens in a new tab)
GETPlayer recent matches
/tennis/v2/h2h/recent/{tour_type}/{player_id_or_name}
CORE PREFIX
Returns a player’s recent matches with opponents, results, tournament details, rounds, surfaces, scores and dates.
Open this endpoint in the documentation (opens in a new tab)
GETPlayer-vs-player recent event
/tennis/v2/h2h/player-vs-player/recent-event/{tour_type}/{player1_id_or_name}/{player2_id_or_name}
CORE PREFIX
Returns the most recent or upcoming event between two players with match, tournament, status, form and player context.
Open this endpoint in the documentation (opens in a new tab)
GETPlayer recent statistics
/tennis/v2/h2h/recent-stats/{tour_type}/{player_id_or_name}
CORE PREFIX
Returns recent serving, returning, break-point, season, deciding-set and surface performance statistics for a player.
Open this endpoint in the documentation (opens in a new tab)
GETH2H performance breakdown
/tennis/v2/h2h/breakdown/{tour_type}/{player_id_or_name}
CORE PREFIX
Returns a broad player breakdown covering achievements, tournament levels, surfaces, serve and return performance, tiebreaks and opponent-ranking context.
/tennis/v2/h2h/breakdown/{player_id_or_name}
GETPlayer comparison filters
/tennis/v2/h2h/filters/{player1_id_or_name}/{player2_id_or_name}/{tour_type}/vs
CORE PREFIX
Returns valid surfaces, rounds, tournament levels, tournaments and seasons for player-vs-player comparison queries.
Open this endpoint in the documentation (opens in a new tab)
GETLast match played
/tennis/v2/h2h/last-match-played/{tour_type}/{player_id_or_name}
CORE PREFIX
Returns a player’s most recently completed match with the result, score, tournament, round and duration where available.
GETPlayer rivalries
/tennis/v2/h2h/rivalries/{tour_type}/{player_id_or_name}
CORE PREFIX
Returns a player’s leading rivalries with opponent names, head-to-head records and total meetings.
Open this endpoint in the documentation (opens in a new tab)
GETCurrent-event statistics
/tennis/v2/h2h/current/{tour_type}/{player1_id_or_name}/{player2_id_or_name}
CORE PREFIX
Returns current matchup statistics such as recent form, service performance, break points, holds, tiebreaks, duration and points won.
Open this endpoint in the documentation (opens in a new tab)
GETFull H2H history
/tennis/v2/h2h/history/{tour_type}/{player1_id_or_name}/{player2_id_or_name}
CORE PREFIX
Returns the complete past-match history between two players, with optional surface filtering.
Open this endpoint in the documentation (opens in a new tab)
GETInteresting potential matchups
/tennis/v2/interesting-h2h/{tour_type}
CORE PREFIX
Ranks notable potential head-to-head matchups from current possible fixtures and includes each pair’s career rivalry record.
Open this endpoint in the documentation (opens in a new tab)04 7 documented routesRankings APIRetrieve current singles and doubles rankings, year-to-date races, Top 10 lists, historical ranking snapshots and complete date-specific ranking tables. Explore endpoints
Open any route for fields, inputs, use cases and a direct documentation link.
Module documentation ↗
GETSingles rankings
/tennis/v2/{tour_type}/ranking/singles
CORE PREFIX
Current singles rankings with position, points and optional country/date filters.
Open this endpoint in the documentation (opens in a new tab)
GETDoubles rankings
/tennis/v2/{tour_type}/ranking/doubles
CORE PREFIX
Current doubles rankings for ATP or WTA.
Open this endpoint in the documentation (opens in a new tab)
GETRace rankings
/tennis/v2/{tour_type}/ranking/singles?race=true
CORE PREFIX
Year-to-date Race standings instead of the standard rolling rankings.
Open this endpoint in the documentation (opens in a new tab)
GETTop 10
/tennis/v2/ranking/{tour_type}/top
CORE PREFIX
Latest top 10 with points, country codes and ranking date.
Open this endpoint in the documentation (opens in a new tab)
GETRanking filters
/tennis/v2/ranking/{tour_type}/filters
CORE PREFIX
Available metadata for building ranking filter controls.
Open this endpoint in the documentation (opens in a new tab)
GETPlayer ranking history
/tennis/v2/ranking/{tour_type}/player/{player_id}/history
CORE PREFIX
Historical ranking snapshots for charting movement through time.
Open this endpoint in the documentation (opens in a new tab)
GETFull rankings by date/type
/tennis/v2/ranking/{tour_type}
CORE PREFIX
Complete rankings list by singles/doubles group and ranking date.
Open this endpoint in the documentation (opens in a new tab)05 13 documented routesTournaments APIPower event calendars, tournament landing pages, year-by-year history, draws, seed lists, points tables, champions and historical results. Explore endpoints
Open any route for fields, inputs, use cases and a direct documentation link.
Module documentation ↗
GETTournament calendar
/tennis/v2/{tour_type}/tournament/calendar/{year}
CORE PREFIX
All tournaments in a calendar year, filterable by tier and court, with optional prize/ranking-point data.
Open this endpoint in the documentation (opens in a new tab)
GETTournament info
/tennis/v2/{tour_type}/tournament/info/{season_id}
CORE PREFIX
Detailed information for one tournament season, including court, country, rank and optional prize/rating information.
Open this endpoint in the documentation (opens in a new tab)
GETTournament seasons
/tennis/v2/{tour_type}/tournament/seasons/{season_id}
CORE PREFIX
Every yearly edition linked to the same tournament family.
Open this endpoint in the documentation (opens in a new tab)
GETPast champions
/tennis/v2/{tour_type}/tournament/past-champtions/{season_id}
CORE PREFIX
Returns historical champions for the same tournament family. The documented route uses the legacy spelling past-champtions.
GETTournament results
/tennis/v2/{tour_type}/tournament/results/{season_id}
CORE PREFIX
Full historical match results for a tournament season.
Open this endpoint in the documentation (opens in a new tab)
GETTournament draws
/tennis/v2/tournament/{tour_type}/{tournament}/{year}/draws
CORE PREFIX
Complete bracket with rounds, matchups, seeds, player information, scores and match status.
Open this endpoint in the documentation (opens in a new tab)
GETTournament seeds by year
/tennis/v2/tournament/{tour_type}/{tournament}/{year}/seeds
CORE PREFIX
Returns seeded players and official seed numbers for a named tournament edition.
Open this endpoint in the documentation (opens in a new tab)
GETAvailable tournament years
/tennis/v2/tournament/{tour_type}/{tournament}
CORE PREFIX
Returns all years for which historical data is available for a named tournament.
Open this endpoint in the documentation (opens in a new tab)
GETMost tournament victories
/tennis/v2/tournament/{tour_type}/{tournament}/most-victories
CORE PREFIX
Returns the players with the most match victories at a tournament across all available years.
Open this endpoint in the documentation (opens in a new tab)
GETCurrent tournament seeds
/tennis/v2/tournament/{tour_type}/{tournament}/seeds
CORE PREFIX
Returns seedings for the current edition of a named tournament without requiring a year.
Open this endpoint in the documentation (opens in a new tab)
GETTournament details by year
/tennis/v2/tournament/{tour_type}/{tournament}/{year}
CORE PREFIX
Returns tournament metadata for a specific edition, including surface, level, prize money and dates where available.
Open this endpoint in the documentation (opens in a new tab)
GETRanking-points breakdown
/tennis/v2/tournament/{tour_type}/{tournament}/{year}/points
CORE PREFIX
Returns ranking points awarded for each round of a named tournament edition.
Open this endpoint in the documentation (opens in a new tab)
GETPast champions by name and year
/tennis/v2/tournament/{tour_type}/{tournament}/{year}/past-champions
CORE PREFIX
Returns previous winners of a named tournament up to and including the selected year.
Open this endpoint in the documentation (opens in a new tab)06 6 documented routesUpcoming Matches & PredictionsDiscover upcoming ATP and WTA matches, surface and tournament filters, priority matches and model-driven prediction output. Explore endpoints
Open any route for fields, inputs, use cases and a direct documentation link.
Module documentation ↗
GETAll upcoming matches
/tennis/v2/upcoming/matches
CORE PREFIX
Upcoming scheduled matches across ATP and WTA with pagination and tournament filtering.
Open this endpoint in the documentation (opens in a new tab)
GETTop matches today
/tennis/v2/upcoming/top-tennis-matches-today/{tour_type}
CORE PREFIX
The most significant scheduled matches today, ranked by importance.
Open this endpoint in the documentation (opens in a new tab)
GETMatch prediction
/tennis/v2/upcoming/match-prediction/{tour_type}/{player1}/{player2}
ULTRA / MEGA
Data-driven prediction information for an upcoming matchup.
Open this endpoint in the documentation (opens in a new tab)
GETUpcoming filters by tour
/tennis/v2/upcoming/filters/{tour_type}
CORE PREFIX
Available tournaments, rounds and surfaces for one tour's upcoming matches.
Open this endpoint in the documentation (opens in a new tab)
GETAll upcoming filters
/tennis/v2/upcoming/filters
CORE PREFIX
Available filter values across upcoming-match data.
Open this endpoint in the documentation (opens in a new tab)
GETUpcoming matches by tour
/tennis/v2/upcoming/matches/{tour_type}
CORE PREFIX
Upcoming matches for ATP or WTA, with singles/doubles and pagination options.
Open this endpoint in the documentation (opens in a new tab)07 4 documented routesPotential Fixtures APIExpose matchups that can still occur based on active tournament draws—useful for bracket scenarios, editorial planning and possible-opponent tools. Explore endpoints
Open any route for fields, inputs, use cases and a direct documentation link.
Module documentation ↗
GETAll potential fixtures
/tennis/v2/potential-fixtures/{tour_type}
CORE PREFIX
Possible future pairings based on active tournament draws.
Open this endpoint in the documentation (opens in a new tab)
GETPotential fixtures by tournament
/tennis/v2/potential-fixtures/{tour_type}/tournament/{tour_id_or_name}
CORE PREFIX
Possible pairings that may occur in one selected tournament.
Open this endpoint in the documentation (opens in a new tab)
GETPotential fixtures by player
/tennis/v2/potential-fixtures/{tour_type}/player/{player_id_or_name}
CORE PREFIX
Possible future opponents and rounds for one player.
Open this endpoint in the documentation (opens in a new tab)
GETActive players
/tennis/v2/potential-fixtures/{tour_type}/active-players
CORE PREFIX
Players currently alive in active draws and therefore associated with potential future fixtures.
Open this endpoint in the documentation (opens in a new tab)08 15 documented routesLive Events & Odds APIUse the extended API prefix for live-event discovery, current score state, event timelines, point-by-point data, bookmakers, markets and odds analytics. Explore endpoints
Open any route for fields, inputs, use cases and a direct documentation link.
Module documentation ↗
GETUpcoming live-system events
/tennis/v2/extend/api/events/upcoming/{tour_type}
LIVE PREFIX
Paginated upcoming events from the live-event system.
Open this endpoint in the documentation (opens in a new tab)
GETLive event count
/tennis/v2/extend/api/events/live/count
LIVE PREFIX
Returns the number of matches currently live.
Open this endpoint in the documentation (opens in a new tab)
GETLive events
/tennis/v2/extend/api/events/live
LIVE PREFIX
Live matches with participants, tournament, score, point state, status, timestamp and mapping back to the core API.
Open this endpoint in the documentation (opens in a new tab)
GETEvent by players/date
/tennis/v2/extend/api/event/get/{player1}/{player2}/{date_only}
LIVE PREFIX
Detailed match state including scores, statistics and timeline/event information.
Open this endpoint in the documentation (opens in a new tab)
GETBookmaker lookup
/tennis/v2/extend/api/bookmakers/all
ULTRA / MEGA
Returns the bookmakers available to the odds endpoints.
Open this endpoint in the documentation (opens in a new tab)
GETAll betting markets
/tennis/v2/extend/api/markets/all
ULTRA / MEGA
Lookup list of available betting-market definitions.
Open this endpoint in the documentation (opens in a new tab)
GETPre-match odds
/tennis/v2/extend/api/odds/pre-match/{event_id}
ULTRA / MEGA
Latest pre-match odds by event, market, bookmaker, line and outcome.
Open this endpoint in the documentation (opens in a new tab)
GETCompare odds
/tennis/v2/extend/api/odds/compare/{event_id}
ULTRA / MEGA
Compares a selected market across available bookmakers.
Open this endpoint in the documentation (opens in a new tab)
GETLast 10 odds movements
/tennis/v2/extend/api/odds/summary/movements/last-10/{event_id}
ULTRA / MEGA
Returns the ten most recent odds movements across markets and bookmakers for an event.
Open this endpoint in the documentation (opens in a new tab)
GETLive score by event
/tennis/v2/extend/api/event/live-score/get/{event_id}
LIVE PREFIX
Returns the current score for an event while that event is live.
Open this endpoint in the documentation (opens in a new tab)
GETPoint-by-point data
/tennis/v2/extend/api/event/pbp/{player1_id}/{player2_id}/{tourId}/{roundId}
LIVE PREFIX
Returns point-by-point event data identified by the two players, tournament and round.
Open this endpoint in the documentation (opens in a new tab)
GETEvent timeline
/tennis/v2/extend/api/event/timeline/{event_id}
LIVE PREFIX
Returns chronological timeline data for an event.
Open this endpoint in the documentation (opens in a new tab)
GETRecent event odds
/tennis/v2/extend/api/event/recent-odds/get/{event_id}
ULTRA / MEGA
Returns recent odds snapshots for an event.
Open this endpoint in the documentation (opens in a new tab)
GETArbitrage analysis
/tennis/v2/extend/api/odds/arbitrage/{event_id}?market_id={marketId}
ULTRA / MEGA
Compares best prices across bookmakers and reports whether an arbitrage opportunity exists, including margin and estimated profit percentage.
Open this endpoint in the documentation (opens in a new tab)
GETBiggest odds movements
/tennis/v2/extend/api/odds/biggest-movements/{event_id}?market_id={marketId}
ULTRA / MEGA
Returns the largest opening-to-closing price movements across bookmakers and markets for an event.
Open this endpoint in the documentation (opens in a new tab)09 6 documented routesReference & Search EndpointsRetrieve the IDs and labels used across the API, and search players and tournaments. Stable lookup tables are good candidates for application-level caching. Explore endpoints
Open any route for fields, inputs, use cases and a direct documentation link.
Module documentation ↗
GETCountries
/tennis/v2/countries
CORE PREFIX
Country names and three-letter acronyms used throughout player and tournament data.
Open this endpoint in the documentation (opens in a new tab)
GETRanking tiers
/tennis/v2/ranking
CORE PREFIX
Tournament-level definitions such as Grand Slam, Masters 1000, ATP/WTA tiers and ITF.
Open this endpoint in the documentation (opens in a new tab)
GETRounds
/tennis/v2/round
CORE PREFIX
Round IDs and labels used by fixtures and historical matches.
Open this endpoint in the documentation (opens in a new tab)
GETCourt surfaces
/tennis/v2/court
CORE PREFIX
Court IDs and surface names used in tournament and fixture filtering.
Open this endpoint in the documentation (opens in a new tab)
GETGlobal search
/tennis/v2/search?search={query}
CORE PREFIX
Case-insensitive player and tournament search across ATP and WTA.
Open this endpoint in the documentation (opens in a new tab)
GETDetailed player search
/tennis/v2/search/{query}
CORE PREFIX
Detailed player search results grouped by category with nationality and birth-date context.
Open this endpoint in the documentation (opens in a new tab)Socket.IO integration is documented separately from the 102 REST routes. MEGA-plan access uses token authentication and can stream live-event and odds updates.
How to combine the endpoints
Most production pages use several routes together rather than displaying a single response in isolation.
Match preview
Start with a fixture, then enrich it with both player profiles, current rankings, H2H records, surface performance and a prediction or odds response where your plan permits.
Player page
Combine profile, status, ranking history, titles, finals, recent matches, match statistics, surface summary and next-match data.
Tournament page
Use the calendar or details route, then add draws, seeds, points, results, champions and fixtures for the selected edition.
Live match centre
Discover a live event, map it to the main API with its match ID, then request live score, point-by-point, timeline and odds data—or subscribe through Socket.IO.
Tennis API integration FAQ
Answers to the most common setup and data-interpretation questions.
Do I need an API key to use these endpoints?
Yes. Requests are authenticated through RapidAPI with X-RapidAPI-Key and X-RapidAPI-Host headers. Keep the key in a server-side environment variable or secrets manager rather than client-side JavaScript.
Can I use itf as the tour_type path value?
No. The documented tour_type values are atp and wta. ITF-level events are included inside those datasets and can be isolated with tournament-rank filters.
Which RapidAPI host should I use?
Use the host associated with the product you subscribed to. The flagship Tennis API host includes core, advanced, prediction, live and odds functionality; specialised products use different hosts with the same relevant path patterns.
What is the difference between fixtures and live events?
Fixture routes focus on scheduled and upcoming matches. Extended live routes provide current event status, scores, points, timelines and related real-time data.
Are the tables in this article live API data?
No. They are representative visual examples designed to show how common responses can be presented. Use an authenticated request when you need current fixtures, rankings, scores or odds.
Start with one fixture request, then layer in the data your product needs.
The flagship product provides the broadest route coverage under one RapidAPI host. Keep credentials server-side, cache stable lookup data and use the documentation links above for the exact response schema of each endpoint.
Editorial note: route names, paths, plan labels and implementation notes were reviewed against the public Tennis API v2 documentation on 24 August 2026. The H2H documentation contains a small number of displayed-route/example mismatches; those are called out on the affected cards. Sample tables are illustrative and are not current fixtures, rankings, scores or odds.