CHARGE_NOT_FOUND

Charge not found: what the CHARGE_NOT_FOUND error means and how to fix it.

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

What this means

You can see no charge with this id: it does not exist, belongs to another project, or belongs to a patient you may not read.

Troubleshooting

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

Retry safely

The same id fails the same way.

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