> For the complete documentation index, see [llms.txt](https://docs.driffle.com/driffle-seller-api-legacy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.driffle.com/driffle-seller-api-legacy/faq/cannot-use-the-api-it-throws-401-403-404-errors.md).

# Cannot use the API, it throws 401/403/404 errors

Following the HTTP standards, you should know that:

* `401 Unauthorized` response code means that you are not authenticated (in simpler terms "not logged in").
* `403 Forbidden` response code means that you are not authorized to access your designated resource.
* `404 Not Found` response code means that the resource you are looking for does not exist.

Having that in mind during the usage of our API you might encounter these in multiple scenarios.

### Reason for receiving "401" errors <a href="#reason-for-receiving-401-errors" id="reason-for-receiving-401-errors"></a>

The reason for getting `401 Unauthorized` errors is simply because you did not provide or provided a wrong `Bearer` `Authorization` header (reference the [Getting Access](https://docs.driffle.com/driffle-seller-api-legacy/guide/getting-started#2.-authorization) section for additional details).

### Reason for receiving "403" errors <a href="#reason-for-receiving-403-errors" id="reason-for-receiving-403-errors"></a>

One of the most common reasons for receiving a `403 Forbidden` is that the issued `access_token` being used is not authorized to access an endpoint or an action is not allowed on the access\_token.

### Reason for receiving "404" errors <a href="#reason-for-receiving-404-errors" id="reason-for-receiving-404-errors"></a>

Make sure to use the right REST API endpoints:

> [https://services.driffle.com/api/seller/legacy/](https://services.driffle.dev/api/seller/legacy/)