Can you subscribe instead of poll, and how far does it fan out?
A push transport that delivers score changes as they happen, addressable per match or across the whole slate, that holds up as the number of subscribers grows.
Why it separates providers
Polling caps your responsiveness at your poll interval and burns your quota doing it. The interesting question is not whether a WebSocket exists but how many clients it holds.
The test you can run
Subscribe to the whole slate, then open more connections and watch for dropped frames or refused connections. Check whether the transport is a real fan-out layer or a connection pinned to a worker thread.
What Live Tennis API measures
measured August 18, 2026
concurrent subscribers, zero failures, staged at 500 / 1,000 / 2,000
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? |
| 04 | Point-by-point | Is there a real per-point record, and does it say where it came from? |
| 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? |