payload_too_large

The uploaded body exceeds the limit for this endpoint.

• A source document is larger than the per-file ceiling.
• A batch call carried more items than the endpoint accepts at once.

• Split the upload. Knowledge ingestion is designed for many small sources rather than one large one, and retrieval quality is better for it.
• Check the current limits in the API reference — they are per-endpoint, not global.

{
  "error": {
    "code": "payload_too_large",
    "message": "The uploaded body exceeds the limit for this endpoint",
    "request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
  },
  "type": "https://integrable.cloud/docs/errors/payload_too_large",
  "title": "Payload Too Large",
  "status": 413,
  "detail": "The uploaded body exceeds the limit for this endpoint",
  "instance": "/api/bots/01a0652b-3713-7ea1-a6c9-2e895389ec34"
}

Branch on error.code, not on the message — the code is stable, the sentence is not. Log request_id either way.

Codes that are easy to confuse with this one, or that show up alongside it:

• unsupported_media_type

Quote the request_id from the response — hello@integrable.cloud. It is what lets us find the exact request. The full list of codes is at Error codes, and the conventions every endpoint shares are in Retries, versioning and limits.