# PROVIDER NOT CONFIGURED

Canonical page: https://docs.ovok.com/errors/provider-not-configured

**HTTP 404.** Stable Problem Details type: [`https://docs.ovok.com/errors/provider-not-configured`](https://docs.ovok.com/errors/provider-not-configured).

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

The requested email or wearable provider has not been set up for this project. Clients should branch on `type` and `status`, not on human-readable `detail` text.

## Troubleshooting [#troubleshooting]

Confirm the provider expected by the route and complete its setup before reading or changing provider-specific configuration. Compare the request with the relevant endpoint's documentation and confirm the authenticated project and environment. Record the request path and `traceId` before escalating; the identifier lets an administrator find server-side context without sharing credentials or patient data.

## Related endpoint guidance [#related-endpoint-guidance]

Use these pages to check the route, project settings, and request requirements associated with this error:

- [Set up email](/email-templates/set-up-email)
- [Email troubleshooting](/email-templates/troubleshooting)
- [Set up wearable providers](/wearables/set-up-providers)
- [Wearables API reference](/wearables/api-reference#provider-setup)

## Retry safely [#retry-safely]

Correct the request, configuration, access or project state described above before retrying. Repeating an unchanged request will normally return the same error; for writes, check whether the first attempt changed state before sending it again. Follow endpoint-specific idempotency and concurrency guidance. Do not retry in a tight loop or use a broader permission or project setting to bypass the check.

## 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 sensitive patient data from the report. The [Error responses guide](/errors) explains the response fields, while the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type audited for this release.