Football API

Errors

Errors come back as JSON.

Error body

The documented errors, 400, 404 and 500, carry the same two fields.

Field Type Required
message string Yes
statusCode number Yes

400 Bad request descriptive error.

400 application/json 
{
  "message": "Descriptive bad request error message.",
  "statusCode": 400
}

404 Match statistics not found.

404 application/json 
{
  "message": "Not Found",
  "statusCode": 404
}

500 Internal server error.

500 application/json 
{
  "message": "Internal server error.",
  "statusCode": 500
}

A 401 or 403 carries a different body, described under status codes.

Status codes

Every Football API endpoint declares 400 and 500. Match statistics also declares 404. Any endpoint can also return 401 or 403 when the key is rejected or missing.

Status Cause
400

Bad request descriptive error. Returned for a malformed request. Read message, which describes the problem.

401

The key was not accepted, and message reads Invalid request token. Check it against the key in your account.

403

The x-rapidapi-key header is missing. This response carries status and error in place of statusCode and message.

404

Match statistics not found. Returned by match statistics when no statistics exist for the match.

500

Internal server error. If it persists, contact support with the request URL and the time it happened.

Plan restrictions

On the Basic and Free plans highlights might have certain restrictions in place. The plan object on a paginated response carries your tier and a message explaining it. See Pagination and limits.

Quota exhausted

When x-ratelimit-requests-remaining reaches zero, you will not be able to make any requests until your daily quota resets. Read that header rather than counting requests yourself.