Skip to main content
Possible error codes common to all requests returned via the error property when a request fails.
When using OAuth 2.0 authentication, errors with HTTP status 400, 401, or 403 follow a different format. See the Error responses with OAuth section in Authentication.

Authentication and authorization errors

These errors include the appropriate HTTP status code in the response:
RESTAURANT_NOT_FOUND
error
HTTP 401 - The restaurant was not found
INVALID_KEY
error
HTTP 401 - The provided API key is not valid
INVALID_AUTH
error
HTTP 401 - Client Id/Secret authentication failed
API_DISABLED
error
HTTP 403 - API access is not enabled for the restaurant
INSUFFICIENT_SCOPE
error
HTTP 403 - Permissions do not cover the required scope for the operation. Additional details are provided in the message field
UNAUTHORIZED
error
HTTP 403 - The API client cannot access the specified resource

Other errors

These errors return HTTP 200 with error details in the response body:
INVALID_ACTION
error
The requested action is not valid
VALIDATION_ERROR
error
The data did not pass validation. Details are provided in the message field
MISSING_PARAMETER
error
Required parameters are missing
RATE_LIMIT_EXCEEDED
error
Exceeded the per-minute call limit
INTERNAL_ERROR
error
A server-side error occurred. Details are provided in the message field