PLAN_NOT_FOUND

Plan not found: what the PLAN_NOT_FOUND error means and how to fix it.

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

What this means

The patient has no plan: no plan was ever set for them through PUT /v1/patient-billing/patients/<patientId>/plan.

Troubleshooting

  1. Treat the patient as having no paid plan.
  2. If your server should have set one, check that its plan webhook reached PUT /v1/patient-billing/patients/<patientId>/plan.

Retry safely

Reading again is safe and answers the same until a plan is set.

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