Tennis API Documentation

Potential Tournament Matchups

ℹ️

Only unfinished events, exact names

Potential fixtures cover today's unfinished events. A finished Grand Slam name correctly returns no events. Use tournament names exactly as returned by this list when calling /potential-fixtures/{tour}/tournament/{name}.

GET/tennis/v2/potential-fixtures/atp

This example uses atp. Use wtafor the women's dataset.Returns all potential upcoming fixtures between players based on the current tournament draw. This endpoint helps identify possible future matchups before they are officially confirmed, making it useful for predictions, tournament analysis, and matchup planning. Only potential pairings are included; no match results or live data are returned.

Path Parameter

Parameter	Required	Type	Description
`atp\|wta`	Yes	string	Dataset to query. `atp` = men's tennis across all supported levels, including Grand Slams, ATP Tour, Challengers and ITF. `wta` = women's tennis across all supported levels, including Grand Slams, WTA Tour and ITF. There is no separate `itf` value.

Query Parameter

Parameter	Required	Type	Description
`pageSize`	No	integer	Results per page. Default: `10`. Core maximum: `500` (larger values are reduced). Example: pageSize=10.
`pageNo`	No	integer	Page number, 1-indexed. Default: `1`. Example: pageNo=1. Use `hasNextPage` in the response to check for more pages.

Example Request: CURL

curl --request GET \
	--url 'https://tennis-api-atp-wta-itf.p.rapidapi.com/tennis/v2/potential-fixtures/atp' \
	--header 'X-RapidAPI-Host: tennis-api-atp-wta-itf.p.rapidapi.com' \
	--header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY'

Potential Tournament Matchups by Tournament

GET/tennis/v2/potential-fixtures/atp/tournament/Phan%20Thiet%204%20Challenger

This example uses atp. Use wtafor the women's dataset.Retrieves all potential upcoming matchups for a specific tournament based on the current tournament draw. The response includes every possible pairing that can still occur in future rounds, along with the corresponding round and draw position.

Path Parameter

Parameter	Required	Type	Description
`atp\|wta`	Yes	string	Dataset to query. `atp` = men's tennis across all supported levels, including Grand Slams, ATP Tour, Challengers and ITF. `wta` = women's tennis across all supported levels, including Grand Slams, WTA Tour and ITF. There is no separate `itf` value.
`tour_id_or_name`	Yes	string	Tournament ID or exact tournament name. Either value can be used to identify the tournament.

Query Parameter

Parameter	Required	Type	Description
`pageSize`	No	integer	Results per page. Default: `10`. Core maximum: `500` (larger values are reduced). Example: pageSize=10.
`pageNo`	No	integer	Page number, 1-indexed. Default: `1`. Example: pageNo=1. Use `hasNextPage` in the response to check for more pages.

Example Request: CURL

curl --request GET \
	--url 'https://tennis-api-atp-wta-itf.p.rapidapi.com/tennis/v2/potential-fixtures/atp/tournament/Phan%20Thiet%204%20Challenger' \
	--header 'X-RapidAPI-Host: tennis-api-atp-wta-itf.p.rapidapi.com' \
	--header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY'

Potential Tournament Matchups by Player

GET/tennis/v2/potential-fixtures/atp/player/Filip%20Peliwo

This example uses atp. Use wtafor the women's dataset.Returns all potential upcoming fixtures for a specific player based on the current tournament draw. The response includes every possible opponent the player may face in future rounds, along with the projected round and draw position. This endpoint is useful for analyzing a player's possible tournament path and upcoming match scenarios.

Path Parameter

Parameter	Required	Type	Description
`atp\|wta`	Yes	string	Dataset to query. `atp` = men's tennis across all supported levels, including Grand Slams, ATP Tour, Challengers and ITF. `wta` = women's tennis across all supported levels, including Grand Slams, WTA Tour and ITF. There is no separate `itf` value.
`player_id_or_name`	Yes	string	URL-encoded display name (`Carlos%20Alcaraz`) or numeric ID (`68074`). Hyphenated slugs such as `alcaraz-carlos` return `{"err":"Player not found"}`.

Query Parameter

Parameter	Required	Type	Description
`pageSize`	No	integer	Results per page. Default: `10`. Core maximum: `500` (larger values are reduced). Example: pageSize=10.
`pageNo`	No	integer	Page number, 1-indexed. Default: `1`. Example: pageNo=1. Use `hasNextPage` in the response to check for more pages.

Example Request: CURL

curl --request GET \
	--url 'https://tennis-api-atp-wta-itf.p.rapidapi.com/tennis/v2/potential-fixtures/atp/player/Filip%20Peliwo' \
	--header 'X-RapidAPI-Host: tennis-api-atp-wta-itf.p.rapidapi.com' \
	--header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY'

Players Still Active in Draws

GET/tennis/v2/potential-fixtures/atp/active-players

This example uses atp. Use wtafor the women's dataset.Returns a paginated list of players who are currently active in tournament draws and have potential upcoming fixtures. Each record includes the player's name, the tournament they are competing in, the tournament location, and the event year. This endpoint is useful for discovering players with possible future matchups across all active tournaments.

Path Parameter

Parameter	Required	Type	Description
`atp\|wta`	Yes	string	Dataset to query. `atp` = men's tennis across all supported levels, including Grand Slams, ATP Tour, Challengers and ITF. `wta` = women's tennis across all supported levels, including Grand Slams, WTA Tour and ITF. There is no separate `itf` value.

Query Parameter

Parameter	Required	Type	Description
`pageSize`	No	integer	Players to return. Default 20, maximum 100. Also accepts `limit`.
`pageNo`	No	integer	Page number, 1-indexed. Default: `1`. Example: pageNo=1. Use `hasNextPage` in the response to check for more pages.
`limit`	No	integer	Alias of pageSize on this route. Default 20.

Example Request: CURL

curl --request GET \
	--url 'https://tennis-api-atp-wta-itf.p.rapidapi.com/tennis/v2/potential-fixtures/atp/active-players' \
	--header 'X-RapidAPI-Host: tennis-api-atp-wta-itf.p.rapidapi.com' \
	--header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY'