# INVALID_TOKEN

Canonical page: https://docs.ovok.com/errors/invalid-token

**HTTP 401.** Problem type: [`https://docs.ovok.com/errors/invalid-token`](https://docs.ovok.com/errors/invalid-token).

## What this means [#what-this-means]

Signals did not accept the credential on the request. The HTTP Basic client ID or secret was missing or wrong, or the client no longer exists. The `WWW-Authenticate` header names the scheme, `Basic`. Ovok's Signals gateway signs in to Signals with a credential of its own and answers a refusal of it with its own error, so you see this code only when you call Signals directly.

## Troubleshooting [#troubleshooting]

1. Check that the request carries an `Authorization` header with the `Basic` scheme and the client's `clientId:secret`, base64-encoded. A proxy or client wrapper can drop the header.
2. Compare the client ID and secret with the ones issued for this environment. A credential from one environment is refused in another.
3. Check that the client still exists in the tenant. A deleted client's credential is refused.
4. Through Ovok's gateway, send your Ovok access token instead. The gateway adds the Signals credential itself.

## Retry safely [#retry-safely]

Retry with a valid credential. The same credential is refused again. Nothing ran, so a retry is safe.

## If the problem persists [#if-the-problem-persists]

Share the HTTP status, problem `type`, request path, response timestamp and `traceId` with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The [Error responses guide](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
