onelifevibe

Platform API error

payload_too_large

payload_too_large is the Platform API error code for HTTP 413: the request body is too big for the endpoint you called.

Updated November 6, 2026

HTTP status
413
Code
payload_too_large
API
Platform API v1

Returned when

What to do

Example answer

HTTP/1.1 413
content-type: application/json

{
  "error": {
    "code": "payload_too_large",
    "message": "The request body is over <n> bytes."
  }
}

Related errors

What it means

The Platform API returns payload_too_large with HTTP status 413 when the body of your request is bigger than the limit that applies to it. The response uses the standard error shape: {"error":{"code":"…","message":"…","hint":"…"}}. The code field is payload_too_large. The message can show the measured size, as in "The request body is over <n> bytes." Read the message for context, but match on code.

Why you are seeing it

Request bodies are limited to 64 KB. Requests that ingest event data have a 32 KB limit. The two numbers matter when you build one payload for several records or attach large text values: the serialized body can pass your own checks and still be rejected by the API. Use the byte count in the message to see how far over the limit you are, then check which limit applies to the call you are making.

How to fix it

Send less. For list-shaped payloads, page through the data and make several requests rather than one large request. For large content that does not need to travel in the request, keep it on your side and send a reference. Keep requests that ingest event data at or under 32 KB, and keep other request bodies at or under 64 KB. If a body is only slightly over, trim or split the content before you send it again. Do not retry the same body unchanged.

Handling it in code

Branch on the HTTP status and the code value. A check such as status 413 plus body.error.code equals payload_too_large is the reliable path; body.error.message is for logs and display, not control flow. Record code, message, and hint for diagnostics.

When you handle the error, tell the caller what to change: page the data, reduce the body, or send a reference to content stored elsewhere. The related code invalid_json covers malformed JSON if your rewrite breaks the body.

Questions

What are the size limits for OneLifeVibe Platform API request bodies?

Request bodies are limited to 64 KB. Requests that ingest event data are limited to 32 KB. The API returns payload_too_large with HTTP 413 when a body is over the applicable limit.

How do I fix payload_too_large?

Send less data: page through the data or keep large payloads on your side and send a reference. Then retry with the smaller body. Check the byte count in the message against the limit for your request.

Should I match on the error code or the message?

Match on code. The error codes are stable, while the message can include a byte count and is not the contract. The error object has code, message, and hint fields.

Keys, plans and usage live in the console: rotate keys, add webhook endpoints, see the last 30 days.

Open the console Plans

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.