How quickly does a scoring event reach your code?
The delay between a point being recorded upstream and your process being able to act on it. It splits into the provider's processing time and your network transport — and a provider that does not let you separate the two is asking you to take its word.
Why it separates providers
Every vendor in this category advertises a latency number. Almost none publish the method, the sample, or the date, and none of them can be checked from outside.
The test you can run
Open the push feed and compare the two timestamps every frame carries: `published_at - timestamp` is the provider's processing time, and your own receive clock minus `published_at` is transport. If a feed carries only one timestamp, this test cannot be run against it.
What Live Tennis API measures
Not yet measured. This criterion has no published figure. Rather than estimate one, the page says so — and the method that will produce it is written down in advance.
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 |
|---|---|---|
| 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? |
| 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? |