HTTP status codes¶
Below, you will find an overview of common HTTP status codes used in responses throughout our API. These are also documented in the specification for each endpoint.
Tip
On the getting started page, you can find an overview of common problems and how to resolve them. For example, how to deal with an HTTP 401 response.
| Status code | Status | Description |
|---|---|---|
| 200 | OK | The request was successful and the response body contains data. |
| 201 | Created | The object was successfully created. |
| 204 | No content | The request was successful and the response body is empty. |
| 400 | Bad request | Request is invalid (e.g. incorrectly formatted data), see here for more info. |
| 401 | Unauthorized | Credentials are missing or incorrectly formatted, see here for more info. |
| 403 | Forbidden | Credentials are incorrect or have expired, see here for more info. |
| 404 | Not found | Endpoint or resource requested could not be found. Make sure the URL and parameters like id are correct. See the specification for the API version you are using for more info on all available endpoints. |
| 405 | Method not allowed | The HTTP method of your request is not supported by this endpoint. See the specification for the API version you are using for more info on all available endpoints. |
| 422 | Unprocessable entity | The request was well-formed but could not be processed due to validation errors, see here for more info. |
| 429 | Too many requests | The rate limit was reached. See here for more info. |
| 500 | Internal server error | An unexpected error occurred on the server. If this keeps happening, please contact support. |