CLIENT_ERROR
Troubleshoot an unmapped Ovok client error and correct the request before retrying.
Fallback for an unmapped 4xx response. Problem type: https://docs.ovok.com/errors/client-error.
What this means
The request was rejected, but Ovok has no more specific status-based problem page for this 4xx response. An endpoint-specific machine code, when present, takes precedence; otherwise use the HTTP status and the response details to understand what the endpoint rejected.
Troubleshooting
Confirm the base URL, route, active project, HTTP method, and request headers against the endpoint documentation. Then inspect detail and any entries in errors for a rejected field or condition. If the route documents a more specific error code, use that endpoint guidance too. A client error usually needs a request or access change; repeating identical input will not resolve it.
Retry safely
Correct the request or the condition identified by the endpoint first, then submit it once. Do not build client logic that treats every 4xx response as transient or retries it unchanged.
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