besttennisapi
Criterion 07 of 08

How far back does it go, and what survives at that depth?

The span of the historical record, and — separately — which fields survive at each depth. Results, serve statistics and point sequences do not reach equally far back.

Why it separates providers

A backtest is bounded by the shallowest field it needs, not by the deepest year on the marketing page. The free open datasets this field long relied on are no longer available.

The test you can run

Ask for a match from each decade and diff the fields you get back. Find the year each field you depend on actually starts, rather than trusting a single span.

What Live Tennis API measures

Historical depth 97,901

measured September 1, 2026
2013 to 2022 only

Caveat. Coverage of play in those years is 19.3% overall and 44.9% of tour-level — both numbers or neither. ITF and futures are effectively absent. Matches from 1968 to 2012 hold a result and no point sequence.

Method: https://besttennisapi.com/methodology#historical

Check it against us

A free key takes a minute and needs no card. Every criterion on this site is one you can verify against our live service, and the harness will run the same test against any other provider you are evaluating.

The other criteria

#CriterionThe question it answers
01 Latency How quickly does a scoring event reach your code?
02 Completeness What share of matches actually carry every point?
03 Tour coverage Which tours are in scope, and are they equally served?
04 Point-by-point Is there a real per-point record, and does it say where it came from?
05 Streaming Can you subscribe instead of poll, and how far does it fan out?
06 Free tier Can you evaluate it properly before paying, without a card?
08 Spec and SDKs Is the contract machine-readable, and is it kept honest?