Errors
op_request_too_large
413 — the request body exceeds the platform's maximum size for this endpoint.
Last updated
Cause
Matter caps request-body size per endpoint. The default cap is 256 KB for most JSON endpoints, with larger ceilings on file-upload and bulk-import operations. op_request_too_large fires when the on-the-wire request body exceeds the cap. The check runs before JSON parsing so even malformed bodies that happen to be large hit this code.
Common triggers are bulk grant issuance requests that pack too many grants into a single call, a data-import payload that should have been chunked, or a stray attachment that has been inlined as base64 rather than uploaded separately and referenced by id.
Fix
- Read the operation's documented size cap in the API reference. Each endpoint declares it on
x-matter-max-body-sizewhen it differs from the default. - For bulk operations, chunk the payload. Most bulk operations accept up to a documented maximum number of items per request and pagination via cursors.
- For files and attachments, upload the binary via
createFileand reference the returnedfil_*id in the body instead of inlining base64 bytes. - If the workload genuinely needs a larger ceiling, contact the account team — some endpoints can be raised under a written agreement.
Related codes
validation_body_invalid— the body is within the size cap but fails schema validation.op_rate_limit_exceeded— many small requests rather than one large one.