PAYLOAD_TOO_LARGE

Signals request body too large: what the PAYLOAD_TOO_LARGE error means and how to fix it.

HTTP 413. Problem type: https://docs.ovok.com/errors/payload-too-large.

What this means

The request body is larger than Signals accepts, so it refused the request before reading it and stored nothing. The limit is set for each Signals deployment.

Troubleshooting

  1. Measure the serialized body, which is its Content-Length, not the source data. Pretty-printed JSON adds whitespace.
  2. Split a large batch of readings into several smaller requests.
  3. Remove what the route does not need, such as notes or components the reading does not carry.

Retry safely

Send a smaller body. The same body is refused again. Nothing was stored, so the smaller requests start clean.

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