What share of matches actually carry every point?
The proportion of completed matches whose point sequence has no gaps. Not the number of matches with *some* point data — the share where the sequence is whole.
Why it separates providers
A gap-free sample is the difference between a model you can train and a model that silently learns your provider's outages. Coverage counts hide gaps; shares expose them.
The test you can run
Pull a month of completed matches, request each one's point sequence, and count the matches whose per-match completeness verdict says the sequence is whole. Divide by the completed matches in the same window — a ratio, not a total.
What Live Tennis API measures
measured August 19, 2026
over completed matches, January 2023 to date
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? |
| 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? |
| 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? |