Which tours the tennis API covers

Live Tennis API covers ATP, WTA, Challenger and ITF singles, and ATP, WTA and Challenger doubles, through one API and one key.

Use the same endpoints for live scores, results, players and tournaments across these tours. Tour and draw filters let you select the matches your application needs without changing the response format. The counts below describe completed matches in our records within a fixed date window.

ATP tennis API

Read ATP live scores, results, players and tournaments through the shared API endpoints. Our records contain 17,898 completed ATP singles matches in the measured window.

WTA tennis API

The WTA tennis API uses those same endpoints for live scores, results, players and tournaments. The measured window contains 17,074 completed WTA singles matches. A WTA match can use the same score display and result reader as an ATP match.

Challenger tennis API

Challenger live scores and results use the shared match endpoints, with players and tournaments available through the same API. There are 40,796 completed Challenger men singles matches and 6,616 WTA 125 singles matches in the measured window. Keep the draw filter explicit when separating singles from doubles in a results page.

ITF tennis API

The ITF tennis API returns live scores, results, players and tournaments through the same endpoints as the other tours. Our records contain 47,610 completed ITF men singles matches and 47,903 ITF women singles matches in the measured window. Use the gender filter alongside the tour and draw filters to select either group.

Doubles

ATP, WTA and Challenger doubles use the same endpoints for live scores, results, players and tournaments, with the doubles draw filter. The measured window contains 5,646 ATP doubles matches, 5,066 WTA doubles matches and 11,604 Challenger men doubles matches.

Completed match records

Completed matches in our records, 1 January 2023 to 13 November 2026, counted 13 November 2026

These are match counts. They do not measure how much point data is held for a match, or promise that a future fixture will have the same fields.

Point-by-point coverage

Point-by-point coverage is declared per match and is not complete. Check the coverage declaration before building a point sequence or replay. A completed result does not establish that the full point sequence is available.

The point-by-point history documentation explains those declarations. Keep missing point data distinct from a score of zero when you store or display a response.

Choose the data you need

Read the API reference for endpoint parameters and response fields. The live tennis data API page describes current match state. The historical tennis data API page explains working with past matches.

Start with a free API key for live matches and scores. Check pricing for access to historical results and point data. Your plan determines endpoint access, while each match's coverage declaration describes the data held.

Last updated 13 November 2026.