> For the complete documentation index, see [llms.txt](https://docs.exactbuyer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exactbuyer.com/master/errors.md).

# Errors

What HTTP codes do we use for error identification?

ExactBuyer uses standard HTTP status codes for its API requests in order to help developers find out what exactly went wrong with a request.

| Status Code | Title                 | Description                                                                        |
| ----------- | --------------------- | ---------------------------------------------------------------------------------- |
| 200         | OK                    | Successful request                                                                 |
| 400         | Bad Request           | Badly formatted request                                                            |
| 401         | Unauthorised          | API key is invalid                                                                 |
| 403         | Forbidden             | Insufficient credits                                                               |
| 404         | Not Found             | No resource found for the request                                                  |
| 409         | Conflict              | Resource that your are trying to PUT is in conflict with pre-existing resource(s). |
| 429         | Too Many Requests     | Request rate is exceeding the rate limit of 200 requests per minute                |
| 5XX         | Internal Server Error | Something went wrong on ExactBuyer's end                                           |

&#x20;
