Documentation menu

Errors

Errors always come back as JSON, with an error and, most of the time, a message explaining what went wrong.

Status	When	What to do
`400`	A filter value doesn't make sense, like an unknown sort field or a year in the future	Read `message` — it says what's wrong
`401`	The token is missing or invalid	Check the `Authorization` header (Authentication)
`404`	The game doesn't exist	Check the app ID
`422`	An unknown parameter or an invalid value	Read `errors` — it lists each problem by parameter
`429`	You used all the requests in your plan for this cycle	Wait for the reset (Request limits)

Examples

400 — a value that doesn't make sense

{
  "error": "Bad Request",
  "message": "Invalid sort field. Allowed fields are: name, developer, publisher, release_date, ..."
}

404 — game not found

{ "error": "Not Found", "message": "No game found with ID 1" }

422 — invalid parameters

{
  "error": "Validation Error",
  "message": "Some parameters are invalid",
  "errors": {
    "develper": ["The parameter 'develper' does not exist. Did you mean 'developer'?"],
    "per_page": ["The per page field must not be greater than 100."]
  }
}