Tennis API Documentation

Get All Potential Fixtures

GET/tennis/v2/potential-fixtures/{tour_type}

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	Description
`tour_type`	Yes	Tour category. Allowed values: `atp`, `wta`.

Query Parameter

Parameter	Required	Description
`pageSize`	No	Results per page. Default: `10`. Example: pageSize=10.
`pageNo`	No	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'

Get Potential Fixtures By Tournament

GET/tennis/v2/potential-fixtures/{tour_type}/tournament/{tour_id_or_name}

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	Description
`tour_type`	Yes	Tour category. Allowed values: `atp`, `wta`.
`tour_id_or_name`	Yes	Tournament ID or exact tournament name. Either value can be used to identify the tournament.

Query Parameter

Parameter	Required	Description
`pageSize`	No	Results per page. Default: `10`. Example: pageSize=10.
`pageNo`	No	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/National Bank Open - Montreal' \
	--header 'X-RapidAPI-Host: tennis-api-atp-wta-itf.p.rapidapi.com' \
	--header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY'

Get Potential Fixtures By Player

GET/tennis/v2/potential-fixtures/{tour_type}/player/{player_id_or_name}

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	Description
`tour_type`	Yes	Tour category. Allowed values: `atp`, `wta`.
`player_id_or_name`	Yes	Can be either the player's name or numeric player ID.

Query Parameter

Parameter	Required	Description
`pageSize`	No	Results per page. Default: `10`. Example: pageSize=10.
`pageNo`	No	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/Cameron Norrie' \
	--header 'X-RapidAPI-Host: tennis-api-atp-wta-itf.p.rapidapi.com' \
	--header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY'

Get Active Players From Potential Fixtures

GET/tennis/v2/potential-fixtures/{tour_type}/active-players

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	Description
`tour_type`	Yes	Tour category. Allowed values: `atp`, `wta`.

Query Parameter

Parameter	Required	Description
`pageSize`	No	Results per page. Default: `10`. Example: pageSize=10.
`pageNo`	No	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/active-players' \
	--header 'X-RapidAPI-Host: tennis-api-atp-wta-itf.p.rapidapi.com' \
	--header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY'