MALFORMED_REQUEST
Find and correct the malformed parts of an Ovok API request.
HTTP 400. Problem type: https://docs.ovok.com/errors/malformed-request.
What this means
Ovok could not parse the request or the request does not match the format expected by the endpoint. This is different from a request whose parsed values fail business or field validation.
Troubleshooting
Check that the URL and query string are correctly encoded, the JSON is valid, and each value uses the expected shape and type. Compare the method, path, required headers, and request fields with the endpoint documentation. Inspect detail and errors for a specific location; when they do not identify it, reduce the request to the smallest documented example and add fields back until the problem returns.
Retry safely
Correct the syntax or request format before sending it again. Do not retry unchanged input; use the validation error guidance when the request parses but a field value is invalid.
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