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).

Before reaching out to support with an error, please be aware that 99% of all reported errors are, in fact, user errors. Therefore, please carefully check your code before contacting Protocol support.

Status codes

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

Name
200
Description
A 200 status code indicates a successful response.
Name
400
Description
A 400 status code indicates a client error . problem.
Name
500
Description
A 500 status code indicates a server error .

Error types

Whenever a request is unsuccessful, the Protocol API will return an error response with an error type and 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 the two error types supported by the Protocol API — use these to understand what you have done wrong.

Name
error
Description
This means that we made an error, which is highly speculative and unlikely.
Name
invalid_request
Description
This means that you made an error, which is much more likely.

Error response


    {
    "error": true,
    "message": "Api Key not found"
    }