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

# Troubleshooting

> Learn how to diagnose and resolve common problems for the Endor Labs REST API.

For a full list of error code descriptions, see [Errors](/developers-api/rest-api/using-the-rest-api/errors).

## Invalid authorization

If Endor Labs can't verify your access token (for example, it's empty or expired), Endor Labs terminates the request and returns an invalid authorization response.

```json theme={null}
{
    "code": 16,
    "message": "Invalid authorization header: Bearer",
    "details": [
        {
            "@type": "type.googleapis.com/internal.endor.ai.rpc.v1.HTTPErrorInfo",
            "status_code": 401
        }
    ]
}
```

### Remediation

Try creating a new token or, if you have a valid API key and secret in your `~/.endorctl/config.yaml` file, unsetting the environment variable (`unset ENDOR_TOKEN`).

For more information, see [Authentication](/developers-api/rest-api/authentication).

## Permission Denied

If your access token lacks the required permissions for a namespace or operation, Endor Labs terminates the request and returns an unauthorized response.

```json theme={null}
{
  "code": 7,
  "message": "Unauthorized request for given endpoint",
  "details": [
    {
      "@type": "type.googleapis.com/internal.endor.ai.rpc.v1.HTTPErrorInfo",
      "status_code": 403
    }
  ]
}
```

### Remediation

Check the value of the `ENDOR_NAMESPACE` environment variable, the variable with the same name in the `~/.endorctl/config.yaml file`, or the API endpoint URL.

For more information, see [Authentication](/developers-api/rest-api/authentication).

## Context deadline exceeded

If it takes too long to process an API request, Endor Labs will terminate the request and you will receive a timeout response and a "context deadline exceeded" message.

```json theme={null}
{
    "code": 4,
    "message": "context deadline exceeded",
    "details": []
}
```

Endor Labs reserves the right to change the timeout window to protect the speed and reliability of the API.

### Remediation

You can [increase the request timeout limit](/developers-api/rest-api/using-the-rest-api/getting-started#request-timeout) or you can try to [simplify your request](/developers-api/rest-api/using-the-rest-api/getting-started#list-parameters). For instance, if you are requesting 100 items per page, try requesting fewer items.

For more information, see [Best practices](/developers-api/rest-api/using-the-rest-api/best-practices).

## Invalid argument

If a request is missing a required field, or includes a non-existent field, Endor Labs will return an "invalid argument" response.
The response `message` field contains details about the error, such as the field name and the specific problem with it.

For example, Endor Labs returns the following response if you request findings with the field mask `uui` instead of `uuid`:

```json theme={null}
{
  "code": 3,
  "message": "mask: proto: invalid path "uui" for message "internal.endor.ai.endor.v1.Finding"",
  "details": [
    {
      "@type": "type.googleapis.com/internal.endor.ai.rpc.v1.HTTPErrorInfo",
      "status_code": 400
    }
  ]
}
```

### PATCH requests

Here is an example response to an PATCH (update) request that sent a Finding as the payload instead of an [UpdateFinding](/api-reference/findingservice/updatefinding):

```json theme={null}
{
  "code": 3,
  "message": "invalid Finding.Meta: value is required; invalid Finding.Spec: value is required",
  "details": [
    {
      "@type": "type.googleapis.com/internal.endor.ai.rpc.v1.HTTPErrorInfo",
      "status_code": 400
    }
  ]
}
```

#### Remediation

Make sure to use the right data structure as the payload for your PATCH requests. For example:

```json theme={null}
{
  "request" : {
    "update_mask": "meta.tags"
  },
  "object" : {
    "uuid" : "<uuid>",
    "meta" : {
      "tags": [
        "<tags>"
      ]
    }
  }
}
```