# `invalid_token`

> For the complete documentation index, see [llms.txt](https://www.shortsintel.com/llms.txt). Every docs page is also available as markdown: add .md to its URL. To connect, read [agents.md](https://www.shortsintel.com/agents.md).

An OAuth access token failed verification.

## Status

HTTP `401`, title `Invalid token`. One of the [credentials](https://www.shortsintel.com/docs/reference/errors#credentials) errors. Branch on `code`, never on the status or the prose.

Retryable: no. Every body carries this as `retryable: false`, beside `action` and `remedy`: the same request will fail again until the request changes or a person acts.

## Common causes

- The token expired.
- The token was minted for another audience or issuer.
- The token was altered or signed with an unknown key.

## What to do

Action: Refresh the access token, then retry once with the new token.

An access token failed verification — bad, expired, or minted for something else. Refresh it and retry once.

## Example

The body arrives as `application/problem+json`, with `retryable` and the `remedy` above. Most responses add `detail` about the occurrence, and some add fields of their own.

```json
{
  "type": "https://www.shortsintel.com/docs/reference/errors/invalid_token",
  "title": "Invalid token",
  "status": 401,
  "code": "invalid_token",
  "retryable": false,
  "action": "Refresh the access token, then retry once with the new token.",
  "remedy": "An access token failed verification — bad, expired, or minted for something else. Refresh it and retry once."
}
```

## Related

- [MCP quickstart](https://www.shortsintel.com/docs/mcp)
- [Authentication and limits](https://www.shortsintel.com/docs/concepts/authentication-and-limits)
- [Every error code](https://www.shortsintel.com/docs/reference/errors)

[Previous key_expired](https://www.shortsintel.com/docs/reference/errors/key_expired)[Next organization_not_selected](https://www.shortsintel.com/docs/reference/errors/organization_not_selected)
