Rate limits & plans

Two independent limits apply to every authenticated /v2 call, per account (shared by all its keys — more keys do not raise them):

• Quota: requests per UTC calendar month on Starter, Pro and Business (resetting at 00:00 UTC on the 1st), per UTC day on Free (resetting at 00:00 UTC). Every response carries RateLimit-Limit (the quota), RateLimit-Remaining (requests left in it) and RateLimit-Reset (seconds until it resets). Going over returns 429 quota_exceeded with Retry-After set to the seconds until the reset.
• Rate: requests per minute, in fixed one-minute windows (burst protection; the figures are in the plan table below). It has no headers of its own: going over returns 429 rate_limited with Retry-After (seconds until the next minute) and does not count against the quota.

Ticket requests count like any other call. Requests rejected with 401 or 403 endpoint_not_in_plan are not counted. Every plan gets every sport and the core data; plans differ in volume, rate, history depth and WebSocket grade, and the premium endpoints — our win-probability model, AI commentary, and the match and player analytics (shot map, heatmap, average positions, momentum, play by play, point by point, best players, top players, the player-statistics explorer) — are Pro and Business only, marked Pro + Business on their pages. Free and Starter keys get 403 endpoint_not_in_plan on them.

History: a plan reaches back a set number of days from the start of today (UTC). A fixture that kicked off earlier, a day list of an earlier date, and a league season that ended earlier (standings, rounds, top players and teams, team and player season statistics) answer 403 history_not_in_plan, with historyFrom — the first day you can read — in the error. Fixture lists (a team's or player's fixtures, a round) leave the older fixtures out and say so in meta.historyFrom. Upcoming and live data are never limited. These refusals count against the quota like any other call.