CONTENT_TOO_LARGE
Reduce an Ovok request body that exceeds the endpoint's accepted size.
HTTP 413. Problem type: https://docs.ovok.com/errors/content-too-large.
What this means
The request body is larger than the endpoint or an intermediary can accept. The response does not establish a universal size limit; limits can depend on the route and deployment.
Troubleshooting
Measure the serialized request body, not only the size of the source file or object. Look for large embedded content, repeated fields, or a batch that can be divided. Check the endpoint documentation for any route-specific limits and confirm that your client is sending only the fields the operation needs.
Retry safely
Send a smaller request. If you split a batch, follow that endpoint's ordering and relationship rules so that dependent records remain valid. Retrying the same body unchanged will fail again.
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