# INVALID_CREDENTIALS

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

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

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

Ovok checked the push provider's credentials before storing them, and the provider refused them, or they are not credentials that provider takes. Nothing was stored.

## Troubleshooting [#troubleshooting]

1. For `fcm`, send the whole service account key file of the Firebase project, as text. Google must accept it: check that the key was not deleted or disabled in the Google Cloud console.
2. For `apns`, send the `.p8` auth key with the `keyId` and `teamId` it was made under. The key must be an APNs key from the Apple Developer account.
3. For `relay`, use an https URL whose host resolves to public addresses only. Private, loopback and link-local addresses are refused. The `detail` says which check failed.

## Retry safely [#retry-safely]

Nothing was stored. Retry with corrected credentials. Keep keys out of logs and support messages.

## 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.
