Live Tennis APIRequest budget calculator for the Live Tennis API
Enter how many matches you follow at once, how often you poll and how many hours a day. You get your requests per day and per minute, and the smallest plan that covers both.
Your polling load
- Requests a day
- 2,880
- Requests in the busiest minute
- 8
Smallest plan that fits: Pro, $29.99 a month
Pro allows 10,000 requests a day and 300 a minute.
| Plan | Price a month | Requests a day | Requests a minute | Covers this load |
|---|---|---|---|---|
| Free | $0 | 100 | 30 | No, over the daily quota |
| Basic | $9.99 | 1,000 | 60 | No, over the daily quota |
| Pro | $29.99 | 10,000 | 300 | Yes, the smallest fit |
| Ultra | $99.99 | 500,000 | 600 | Yes |
The page address holds your numbers, so you can bookmark a result or send it to someone. A plan also decides which data you can read. This calculator covers request volume only, and the pricing page lists what each plan includes.
Get a free keyRead the rate limit docs
How many requests does polling use?
Following 4 matches every 30 seconds for 6 hours a day uses 2,880 requests a day. The busiest minute has 8 requests. The Live Tennis API Pro plan is the smallest that covers both, at $29.99 a month.
How does the calculator work out the load?
Polls a day are the hours times 3,600, divided by the seconds between polls and rounded up. Requests a day are the polls times the matches.
The busiest minute holds 60 divided by the seconds between polls, rounded up, and never fewer than one poll. Multiply that by the matches. This assumes you poll every match on the same tick. A timer that drifts can put one extra poll in a minute, so leave some room under the per-minute limit.
A plan covers the load when two things hold. Its daily quota is at least the requests a day. Its per-minute limit is at least the busiest minute.
What counts as a request?
Each call the API answers is one request. GET /matches?status=live returns the slate of live matches, and GET /matches/{matchId}/score reads one match. The calculator counts one request per match on each poll. If one call covers several matches for you, enter the calls you make per poll instead.
Refused requests do not spend the daily allowance, so a 429, 403 or 404 leaves it unchanged. GET /usage shows your plan, your limits and the calls you made today. It still answers after you reach the daily quota.
Do I have to poll?
On the Ultra plan you do not. It includes a WebSocket push feed and webhooks that send score and point changes as they happen. The push feed and webhooks guide has the details.
What happens if I go over a limit?
Past the per-minute limit the API answers 429 with a Retry-After header. Wait that many seconds and send the request again.
Past the daily quota it answers 429 with scope: "day" and resets_at, the time the daily window resets. Stop until then or upgrade. The errors and rate limits guide covers every case.
What if no plan covers my load?
Poll less often, follow fewer matches or use the push feed on Ultra. For a custom quota, write to hello@livetennisapi.com and tell us what you are building.
Quotas, limits and prices match the pricing page. Last checked on 11 November 2026.