Getting Started

Your First Request

Authenticate, pick the correct path family, then make a first fixtures call. Most integration mistakes are wrong prefixes, player identifiers, pagination names, or date formats — those are covered below so you do not have to guess.

Step 1 — Subscribe on RapidAPI

The Tennis API is distributed exclusively through RapidAPI.

1. Visit the Tennis API (ATP, WTA, ITF) listing on RapidAPI.
2. Click Subscribe and select a pricing plan.
3. Copy your X-RapidAPI-Key from the Security tab or the code snippets panel.

Step 2 — Base URL & Headers

Every request targets:

https://tennis-api-atp-wta-itf.p.rapidapi.com

Include these two headers on every request:

Step 3 — URL Structure

There are three path families. They are not interchangeable. Copy the prefix from this table, then append the module path from the reference page.

GET /tennis/v2/{atp|wta}/{module}   core, e.g. /tennis/v2/atp/fixtures
GET /tennis/v2/{module}/…          name-based, e.g. /tennis/v2/profile/Carlos%20Alcaraz
GET /tennis/v2/extend/api/…            live & odds

ATP, WTA, and ITF

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.

Filter by level with TourRank using ids from GET /ranking. Grand Slam is rank_id 4. Challenger / ITF > $10K is 1.

Player & tournament identifiers

Tournament season IDs (core /tournament/info/{seasonid}) are one year-edition of an event. Name-based tournament routes often use the exact tournament name from the calendar (URL-encoded), not that season ID. Live odds use a separate event id. See FAQ: live IDs.

Step 4 — Make Your First Call

Use a dated fixtures URL so the sample stays the same. Today's list (/atp/fixtures with no date) changes throughout the day.

curl --request GET \
	--url 'https://tennis-api-atp-wta-itf.p.rapidapi.com/tennis/v2/atp/fixtures/2026-09-08?pageNo=1&pageSize=2&filter=PlayerGroup:singles' \
	--header 'X-RapidAPI-Host: tennis-api-atp-wta-itf.p.rapidapi.com' \
	--header 'X-RapidAPI-Key: YOUR_RAPIDAPI_KEY'

Pagination

Dates

Query Parameters: include and filter

Core fixtures and several player/H2H lists accept optional include and filter query strings. Filters are not top-level keys.

Empty results vs errors

Data conventions

Rate Limits

A server-side throttle of 100 requests per minute per IP applies to all endpoints. On breach, the API returns:

{
    "statusCode": 429,
    "message": "ThrottlerException: Too Many Requests"
}

Your RapidAPI plan may add a daily or monthly quota on top of this throttle.

Error Handling

The API uses standard HTTP status codes to indicate success or failure. Always check the HTTP status code before processing the response body.

When an error occurs, the response body contains a JSON object with error details:

{
   "error": true,
   "statusCode": 400,
   "message": "Invalid date format. Expected YYYY-MM-DD."
}

Next Steps

Now that you can make requests, explore the individual modules:

• ATP / WTA / ITF coverage and data conventions
• FAQ & Troubleshooting — 403s, IDs, dates, live IDs, empty lists
• Fixtures — match schedule, filters, date-range queries
• Players — core numeric-ID profiles and advanced name-based stats
• Head-to-Head — rivalry records and per-match stats
• Rankings — current lists and historical snapshots
• Tournaments — season IDs, results, draws
• Calendar — year calendar with level names
• Live Event And Odds — live board, odds, point-by-point
• Socket.IO — Mega push updates
• Miscellaneous — countries, courts, rounds, search