API errors

Payload too large

The request body exceeds the 2 MB size limit and was rejected before processing. Nothing was processed or billed.

Error type

https://normbill.com/docs/errors/payload-too-large

HTTP status

413

Common causes

• The invoice JSON — or the XML sent to /v1/invoices/validate or /v1/invoices/parse — is larger than 2 MB.
• Several invoices were batched into a single request.
• A very large free-text note or embedded value inflated the body.

How to fix it

• Send one invoice per request — the API processes a single document at a time.
• Remove or shrink oversized free-text fields.
• Keep the total request body under 2 MB.

The error response format

Every non-2xx response from the API is an RFC 9457 problem-details body (application/problem+json) with at least type, title, status and detail. The type URL links back to this reference.

All error slugs: invalid-request, bad-request, payload-too-large, unauthorized, validation-failed, unparseable-document, plan-limit, quota-exceeded, rate-limited, overage-cap-reached, validate-fair-use, idempotency-key-invalid, idempotency-key-reuse, idempotency-conflict, pdf-unavailable, validator-unavailable, not-ready. Still stuck? Email support@normbill.com or start at the docs overview.