# UNAUTHENTICATED

Canonical page: https://docs.ovok.com/errors/unauthenticated

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

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

The request did not include credentials that Ovok accepts. The token may be missing, expired, invalid, or intended for a different environment.

## Troubleshooting [#troubleshooting]

Check that the request includes the current access token using the authentication scheme required by the API, and confirm that your client is calling the intended environment. If the token may have expired, refresh it or sign in again using the documented authentication flow. Check that a proxy or client wrapper has not removed the authorization header.

## Retry safely [#retry-safely]

Obtain valid credentials and send the request again. Do not retry repeatedly with the same rejected token, and never include the token itself in logs, screenshots, or a support report. If fresh credentials still receive 401, ask an administrator to check the authentication setup.

## 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. Do not include access tokens or sensitive patient data. The [Error responses guide](/errors) explains the response fields and field-level errors.