Is there a real per-point record, and does it say where it came from?
A per-point sequence for a match, with each point's state, and an honest marker distinguishing points observed as they happened from points reconstructed afterwards.
Why it separates providers
Reconstructed points carry no real clock. For anything time-sensitive they are a different product, and a feed that blurs the two is unusable for timing work.
The test you can run
Take a completed match, request its point sequence, and look for a provenance marker on each row. Points we watched live carry a real timestamp; reconstructed rows carry none. If every row looks identical, ask which ones were observed.
What Live Tennis API measures
measured August 27, 2026
matches watched live from 0-0, every point carrying a real timestamp
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
| # | Criterion | The 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? |
| 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? |
| 07 | Historical depth | How far back does it go, and what survives at that depth? |
| 08 | Spec and SDKs | Is the contract machine-readable, and is it kept honest? |