Built for serious tennis products

Everything you need to build a serious tennis product — in one API.

From live match data to historical odds and advanced player intelligence, get the tennis data your product needs through one consistent API.

⚡

Real-Time Match Data

Live scores, match stats, point-by-point action, event timelines, real-time updates and live odds — ready for scoreboards, betting products and data-driven applications.

📊

Advanced Player Intelligence

Go beyond basic H2H with rankings, recent form, surface splits, tournament-specific performance, detailed service and return stats, and deeper comparisons against direct opponents and similar rivals.

💰

Odds & Predictions

Access pre-match odds, in-play odds, odds movement, historical odds going back as far as 2010, and probabilities for upcoming matches. Historical coverage includes Marathon Bet and Pinnacle, with pre-match and live odds from Marathon Bet, Pinnacle, bet365, DraftKings and MelBet.

🎾

Complete Tennis Coverage

Players, matches, fixtures, draws, rankings and tournament analytics across ATP, WTA, ITF, Grand Slams, Masters and Challengers — all through a consistent API.

Real-Time WebSockets

MEGA

MEGA plans include push-based updates for live scores, odds and match events, so you can stream changes as they happen without constant polling.

One API. Live data, deep stats, odds, predictions and the infrastructure to build at scale. If you need support, please contact us at api@tennis-api.com

ℹī¸
Ready to integrate?

Use the Getting Started guide to make your first request in under five minutes. All endpoints are available on RapidAPI.

Understanding Tennis API

URL Structure

Every Tennis API endpoint follows the same URL structure:

https://{host}/tennis/v2/{feature-specific-path}

You only need to determine:

  1. The correct host for your subscribed product.
  2. The correct feature-specific path after/tennis/v2/.
ProductHostPath PrefixWhat it contains
Tennis API - ATP WTA ITFtennis-api-atp-wta-itf.p.rapidapi.com/tennis/v2/
/tennis/v2/ms-api/
/tennis/v2/extend/api/		Complete Tennis API with access to all endpoints, including Core, Tennis Stats API,Tennis Predictions API and Tennis Live API. All endpoints share the common base path/tennis/v2/. Additional features are accessed by extending the path:
  • /tennis/v2/ → Core API (fixtures, rankings, tournaments, draws, players, etc.)
  • /tennis/v2/ms-api/ → Extra advanced features.
  • /tennis/v2/extend/api/ → Live & Odds APIs (live scores, point-by-point, live odds, odds movements, etc.)
Simply keep using tennis-api-atp-wta-itf.p.rapidapi.com as the host and append the appropriate path prefix for the API you want to use.

Quick Start Video

Watch this short interactive guide to make your first API request in under five minutes.

Versioning

The current API version is v2. All endpoints use the path prefix /tennis/v2/.

Authentication

This API is distributed through RapidAPI. Every request must include two headers:

HeaderValue
X-RapidAPI-KeyYour RapidAPI subscription key
X-RapidAPI-HostE.g: tennis-api-atp-wta-itf.p.rapidapi.com
ℹī¸
Where to get your key Subscribe to the Tennis API on RapidAPI to receive your X-RapidAPI-Key. Free and paid tiers are available.

Rate Limits

A global throttle of 100 requests per minute per IP is enforced server-side. Exceeding this limit returns HTTP 429 Too Many Requests. Your RapidAPI plan may impose additional quota limits.

Error Codes

HTTP StatusMeaning
200Success — response body contains the data.
400Bad Request — invalid parameters (e.g. wrong date format, invalid ID).
401Unauthorized — missing or invalid X-RapidAPI-Key.
403Forbidden — wrong host header or plan restriction.
404Not Found — the resource or endpoint does not exist.
429Too Many Requests — rate limit exceeded.
500Internal Server Error — unexpected server issue.