COVERAGE_NOT_FOUND

Coverage not found: what the COVERAGE_NOT_FOUND error means and how to fix it.

HTTP 404. Problem type: https://docs.ovok.com/errors/coverage-not-found.

What this means

You can see no active insurance coverage with this id: it does not exist, was removed, is an app plan rather than insurance, or belongs to a patient you may not read.

Troubleshooting

  1. List the patient's coverages (GET /v1/patient-billing/patients/<patientId>/coverages) and use an id from there.
  2. Check that your access policy lets you read the coverage's patient.

Retry safely

The same id fails the same way. A removed coverage does not come back; add it again instead.

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 explains the response fields, and the machine-code registry lists every endpoint-specific type.

Last updated on

On this page