Latency
How quickly does a scoring event reach your code?
Not yet measured
A published method, not an adjective
Best is not a claim.
Best is not a claim.
It’s a measurement you can run.
There is no single best tennis API — there is the one that survives your test. This site sets out the eight things worth measuring, gives you a test you can run for each, and publishes what Live Tennis API scores on every one, with the date it was measured and the sample it came from.
Check us in one callno key needed
# Every push frame carries two clocks. The gap # between them is our processing time — you do # not have to take our word for any of it. BASE=api.livetennisapi.com/api/public/v1 curl -s "https://$BASE/health" # Then, with a free key (no card): curl -s "https://$BASE/matches?status=live" \ -H "X-API-Key: $KEY"
The eight criteria
01
02
03
04
05
06
07
08
What actually separates a tennis API
Each one has a definition you can argue with, a test you can run against any provider, and — where we have measured it — our own number with its date. Where we have not measured it yet, it says so.
Completeness
What share of matches actually carry every point?
75.0%
Tour coverage
Which tours are in scope, and are they equally served?
Not yet measured
Point-by-point
Is there a real per-point record, and does it say where it came from?
25,747
Streaming
Can you subscribe instead of poll, and how far does it fan out?
2,000
Free tier
Can you evaluate it properly before paying, without a card?
Not yet measured
Historical depth
How far back does it go, and what survives at that depth?
97,901
Spec and SDKs
Is the contract machine-readable, and is it kept honest?
Not yet measured
Latest measurement · 13 September 2026, 11:26 UTC
What the last run saw
Observed availability
100.00%
September 13, 2026 · n=620
single pass, 2026-09-13 11:26 UTC
Health endpoint response
116ms
September 13, 2026 · n=620
single pass, 2026-09-13 11:26 UTC
Read these correctly. They are what one prober saw of our own service from
Nuremberg, Germany (Hetzner nbg1). They are not a comparison with any other provider, and none of them is the
delay between a point being played and the data reaching you — nothing here observes the
court. The method is written down, and
every run is archived so you can check whether a number moved after we
quoted it.
How we measure
Three rules that make a number worth reading
01
Every figure carries its date and its sample
A number with no as-of date and no N is an opinion in a serif font. Ours cannot render without both — the code raises rather than publish an undated claim.
02
The vantage is declared, and it is never our own origin
Latency depends on where you measure from. The prober refuses to run on the host that serves the API, because a loopback would flatter every figure on this page.
03
The caveats travel with the number
Small samples, single vantage, and the difference between what we processed and what you receive are printed next to the figure, not hidden in a footnote.
Open source
Don’t trust this page. Run it yourself.
The harness that produces these numbers is public and MIT-licensed. Point it at our API, or at any other tennis API you are evaluating — it does not know or care which one it is measuring.
git clone https://github.com/livetennisapi/tennis-api-benchmark
cd tennis-api-benchmark
python -m benchmark --base-url https://your-provider.example/v1 \
--api-key "$KEY" --samples 40
Questions
Straight answers
What is the best tennis API?
There is no single answer, and any site that gives you one without telling you what it measured is guessing on your behalf. The useful question is which API survives the test your project actually needs it to pass. This site sets out eight criteria, gives you a test for each, and publishes what Live Tennis API scores — dated, with the sample size.
Who publishes this site?
JSB Holdings LLC, which also operates Live Tennis API. This site is not independent and does not present itself as a neutral review. What it offers instead is a method you can run yourself and raw data you can check.
Why does this site not compare named competitors?
Because a comparison is only worth reading if the person publishing it has measured both sides under identical conditions and has no stake in the result — and we have a stake. So we publish the measuring stick instead: the criteria, the method, and an open-source harness that runs the same tests against any provider, including ones we have never seen.
How do I check a latency claim myself?
Ask the provider for two timestamps on every push frame: when the event occurred and when the frame was published. The gap between them is the provider's processing time, and your own receive clock minus the publication stamp is transport. Live Tennis API carries both. A feed with one timestamp cannot be checked from outside, whatever it claims.
Does a free tier exist, and does it need a card?
Live Tennis API's free tier needs no card and is not a countdown trial — it is a permanent key with published limits, which is what you need to evaluate data quality rather than integration speed.