NOT_ACCEPTABLE
Correct the response format requested by an Ovok API client.
HTTP 406. Problem type: https://docs.ovok.com/errors/not-acceptable.
What this means
The server cannot return a representation accepted by the request. This usually points to response content negotiation, rather than the media type of the request body.
Troubleshooting
Inspect the outgoing Accept header and compare it with the response formats documented for the endpoint. Check whether your HTTP library or API gateway added a restrictive value or requested a format the caller cannot parse. Keep Accept separate from Content-Type: the former describes the response you accept; the latter describes the body you send.
Retry safely
Request a documented response format and retry. If you do not need a special representation, remove the custom Accept restriction according to your client's configuration; changing the request body's Content-Type alone does not fix this error.
If the problem persists
Share the HTTP status, problem type, request path, response timestamp, and traceId with your administrator or support contact. Do not include access tokens or sensitive patient data. The Error responses guide explains the response fields and field-level errors.
Last updated on