Errors

In this guide, we will talk about what happens when something goes wrong while you work with the API. Mistakes happen, and mostly they will be yours, not ours. Let's look at some status codes and error types you might encounter.

You can tell if your request was successful by checking the status code when receiving an API response. If a response comes back unsuccessful, you can use the error type and error message to figure out what has gone wrong and do some rudimentary debugging (before contacting support).


Status codes

Here is a list of the different categories of status codes returned by our APIs. Use these to understand if a request was successful.

  • Name
    2xx
    Type
    required
    Description

    A 2xx status code indicates a successful response.

  • Name
    4xx
    Type
    required
    Description

    A 4xx status code indicates a client error — this means it's a you problem.

  • Name
    5xx
    Type
    required
    Description

    A 5xx status code indicates a server error — you won't be seeing these.


Error types

Whenever a request is unsuccessful, our APIs will return an error response with an error message. You can use this information to understand better what has gone wrong and how to fix it. Most of the error messages are pretty helpful and actionable.

Here is a list of some example error codes from our store API to understand how our api responses looks.

  • Name
    400
    Type
    required
    Description

    Bad request.

  • Name
    403
    Type
    required
    Description

    Forbidden.

  • Name
    404
    Type
    required
    Description

    Store not found.

  • Name
    409
    Type
    required
    Description

    Store name already taken.

  • Name
    500
    Type
    required
    Description

    Internal server error.

Error response

{
  "type": "api_error",
  "message": "No way this is happening!?",
  "documentation_url": "https://pricer.chat/docs/errors/api_error"
}