Skip to main content
Use this page to understand an error response and fix the request that caused it.
Fastest way: ask your AI. Error messages say what’s wrong, and for a misspelled parameter they name the right one. Set up your coding tool once with Build with AI, then paste the request and the full error:

The error format

Every error has the same shape. The HTTP status code is repeated in the body.

Error codes

Examples

There is no date parameter on /football/matches, so this request fails:
The fix: ?team_id=tm_9145&date_from=2026-10-10&date_to=2026-10-10.
No Authorization header:
Other messages you may see: Invalid authorization format. Use: Bearer <api_key> (the key was sent without Bearer ) and Invalid API key.
A misspelled path, such as /football/matchez, returns the same code with the message Route not found.
Calling /football/matches/{match_id}/live-stats for a finished match:
The response includes a Retry-After header with the seconds to wait.

Handle errors in code

Check code, not just the HTTP status. Two errors can share a status but need different handling, such as RATE_LIMITED and USAGE_LIMIT_EXCEEDED.
For 429 responses, wait and retry as shown in Rate limits.