INVALID_EVENT

Webhook event not readable: what the INVALID_EVENT error means and how to fix it.

HTTP 422. Problem type: https://docs.ovok.com/errors/invalid-event.

What this means

A webhook delivery passed the signature check and is valid JSON, but its content is not an event Ovok can read. It is a FHIR store notification that is not an Observation with its id, a Signals delivery that is not a { type, data } event, or an event whose data does not fit its type. Ovok stored and forwarded nothing.

Troubleshooting

  1. Read detail. It names the event type when the data is invalid.
  2. For the FHIR store route, check that the Subscription sends the whole Observation in the body, with channel.payload set to application/fhir+json. The body needs resourceType Observation and an id.
  3. For Signals, send events in schema 2: type and data. A webhook.disabled event needs subscriber, reason and disabledAt in data. Alert and episode events need their documented data fields.
  4. On the shared-tenant route, check that alert and episode events carry patientRefId in data.

Retry safely

Do not resend an unchanged delivery, as it returns the same error. Nothing was stored, so the next delivery after you fix the sender is processed normally.

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