> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vantage.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors

> Understand potential errors and how to correct them when using the Vantage API.

All error responses follow a standard format and are nested under an errors key in the response. The value will be an array of error messages.

```curl theme={null}
{
  "errors": [
    "You are not authorized to view this resource."
  ]
}
```

| Status Code | Message                       | Reason                                                                                                                          |
| ----------- | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| `401`       | Unauthorized or Invalid Token | The token is missing, malformed, expired, or otherwise invalid.                                                                 |
| `403`       | Forbidden                     | The token is valid, but it does not have permission to perform that action or access that workspace or resource.                |
| `404`       | Not Found                     | The requested resource could not be found. This could be due to a mistyped URL or a resource that has been deleted.             |
| `429`       | Too Many Requests             | The user has sent too many requests in a given amount of time. See the [Rate Limiting](/api/rate_limiting) section for details. |
| `500`       | Internal Server Error         | An unexpected condition was encountered. This is a generic error message for server-side issues.                                |
| `422`       | Unprocessable Entity          | The request was well-formed but could not be processed because of validation or other semantic errors in the request data.      |

## Common Authentication and Permission Failures

* If you receive a `401`, verify that your `Authorization: Bearer ...` header is present and that the token value is correct.
* If you receive a `403`, verify that the token has the necessary scope and that it can access the relevant workspace or resource.
* If you are using an Enterprise team-scoped service token, make sure the token's team has access to the workspace you are trying to query or modify.