Errors

In the Bokio API, standard HTTP status codes are used to indicate errors. These status codes provide a standardized way of communicating the outcome of a request. In addition to the status code we provide both a human-readable message field and code field that can be used for machine interpretation of the error. A bokioErrorId is included for Bokio to better be able to help you if you need assistance.

Error Response Format

When an error occurs, the API returns a JSON response with the following structure:

{
  "error": {
    "code": "string",
    "innerCode": "string",
    "message": "string",
    "bokioErrorId": "string"
  }
}

Common error codes are specified in Error codes, but please explore the API operation that you use because there you'll find detailed information on which error codes to expect for the specific operation.

HTTP Status Codes

The following HTTP status codes are commonly used in the Bokio API for error handling:

• 400 Bad Request: The request was invalid or could not be understood by the server.
• 401 Unauthorized: The request requires authentication, but the user is not authenticated.
• 403 Forbidden: The server understood the request, but refuses to authorize it.
• 404 Not Found: The requested resource could not be found.
• 429 Too Many Requests: The request was not processed as rate limits have been surpassed. See Rate Limits.
• 500 Internal Server Error: An unexpected error occurred on the server.

It is important to handle these status codes appropriately in your application to provide a good user experience.

Error codes

🚧

Error codes not defined yet, please check back later.