Predictions & Upcoming Analysis | Tennis API Documentation

All Upcoming Matches

GET/tennis/v2/upcoming/matches?tournament=Rennes%20Challenger&limit=10&page=1

Returns all upcoming scheduled matches across both ATP and WTA tours

Query Parameter

Parameter	Required	Type	Description
`date`	No	string	Match date `YYYY-MM-DD`. Example: `date=2026-09-15`.
`group`	No	string	`singles` or `doubles` only on upcoming lists.
`sortBy`	No	string	Set `sortBy=h2h` to order by head-to-head interest.
`rank`	No	string	Tournament level name from `/upcoming/filters`. Example: `rank=ATP%20250`.
`playerRank`	No	string	Filter by player ranking band when the list supports it. Example: `playerRank=1-50`.
`autoPost`	No	boolean	Internal-style flag. Default `false`. Example: `autoPost=true`.
`tournament`	No	string	Filter by tournament name. Example: tournament=EFG%20Swiss%20Open%20-%20Gstaad
`includeAll`	No	boolean	Include Challenger/ITF and full history where supported. Example: includeAll=true
`page`	No	integer	Page number on advanced routes, starting at 1. Do not send pageNo here. Example: page=1
`limit`	No	integer	Results per page on advanced routes (use page + limit, not pageNo + pageSize). Default varies by endpoint. Example: limit=10

Example Request: CURL

curl --request GET \
	--url 'https://tennis-api-atp-wta-itf.p.rapidapi.com/tennis/v2/upcoming/matches?tournament=Rennes%20Challenger&limit=10&page=1' \
	--header 'X-RapidAPI-Host: tennis-api-atp-wta-itf.p.rapidapi.com' \
	--header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY'

Response Properties

Field	Type	Description
`total`	integer	Total matches matching the filter.
`matches`	array	Page of upcoming matches.
`page / pageNo / pageSize / limit / hasNextPage / totalPages`	mixed	Pagination.
`matches[].tournament`	object	id, name, date, rankId, country, court.
`matches[].player1 / player2`	object	id, name, odd, countryAcr, seed, image.
`matches[].odds`	object	Odds when present: k1, k2, total, ktm, ktb, …
`matches[].h2h`	string	Career H2H as wins-losses, e.g. 0-0.

Top Matches Today

GET/tennis/v2/upcoming/top-tennis-matches-today/atp

This example uses atp. Use wtafor the women's dataset.Returns today’s most significant singles matches (those with a prior H2H).

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.

Example Request: CURL

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

Match Prediction

GET/tennis/v2/upcoming/match-prediction/atp/Lucas%20Poullain/Clement%20Chidekh

This example uses atp. Use wtafor the women's dataset.Returns HTML prediction bullets for this matchup. Optional onlyImp=true keeps the high-signal lines.

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.
`player1`	Yes	string	First player display name (URL-encoded). E.g: Novak%20Djokovic
`player2`	Yes	string	Second player display name (URL-encoded). E.g: Jannik%20Sinner

Query Parameter

Parameter	Required	Type	Description
`includeAll`	No	boolean	Include Challenger/ITF and full history where supported. Example: includeAll=true
`onlyImp`	No	boolean	When true, returns only the high-signal prediction bullets. Example: `onlyImp=true`.

Example Request: CURL

curl --request GET \
	--url 'https://tennis-api-atp-wta-itf.p.rapidapi.com/tennis/v2/upcoming/match-prediction/atp/Lucas%20Poullain/Clement%20Chidekh' \
	--header 'X-RapidAPI-Host: tennis-api-atp-wta-itf.p.rapidapi.com' \
	--header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY'

Response Properties

Field	Type	Description
`paragraph`	string	HTML <ul> of prediction bullets for this matchup.

Upcoming Filters by Tour

GET/tennis/v2/upcoming/filters/atp

This example uses atp. Use wtafor the women's dataset.Returns available filter values (tournaments, rounds, surfaces) for upcoming matches

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.

Example Request: CURL

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

All Upcoming Filters

GET/tennis/v2/upcoming/filters

Returns available all filter values (tournaments, rounds, surfaces) for upcoming matches

Example Request: CURL

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

Upcoming Matches by Tour

GET/tennis/v2/upcoming/matches/atp

This example uses atp. Use wtafor the women's dataset.Returns all upcoming scheduled matches by tour type.

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
`date`	No	string	Match date `YYYY-MM-DD`. Example: `date=2026-09-15`.
`group`	No	string	`singles` or `doubles` only on upcoming lists.
`sortBy`	No	string	Set `sortBy=h2h` to order by head-to-head interest.
`rank`	No	string	Tournament level name from `/upcoming/filters`. Example: `rank=ATP%20250`.
`playerRank`	No	string	Filter by player ranking band when the list supports it. Example: `playerRank=1-50`.
`autoPost`	No	boolean	Internal-style flag. Default `false`. Example: `autoPost=true`.
`tournament`	No	string	Filter by tournament name. Example: tournament=EFG%20Swiss%20Open%20-%20Gstaad
`includeAll`	No	boolean	Include Challenger/ITF and full history where supported. Example: includeAll=true
`page`	No	integer	Page number on advanced routes, starting at 1. Do not send pageNo here. Example: page=1
`limit`	No	integer	Results per page on advanced routes (use page + limit, not pageNo + pageSize). Default varies by endpoint. Example: limit=10

Example Request: CURL

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

Response Properties

Field	Type	Description
`total`	integer	Total matches matching the filter.
`matches`	array	Page of upcoming matches.
`page / pageNo / pageSize / limit / hasNextPage / totalPages`	mixed	Pagination.
`matches[].tournament`	object	id, name, date, rankId, country, court.
`matches[].player1 / player2`	object	id, name, odd, countryAcr, seed, image.
`matches[].odds`	object	Odds when present: k1, k2, total, ktm, ktb, …
`matches[].h2h`	string	Career H2H as wins-losses, e.g. 0-0.