Problems·HTTP 400

malformed-body

The request body could not be parsed.

What it means

The body is not well-formed JSON or XML, so nothing in it could be checked. detail says where parsing stopped.

What to do

Check the body matches its Content-Type, and that the JSON or XML is complete. A body that parses but is wrong gets a 422 instead.

Example

Sent as application/problem+json (RFC 9457). Branch on type, which is stable. Never branch on title or detail, which are prose and may change.

{  "type": "https://www.einvoicing.dev/problems/malformed-body",  "title": "The request body could not be parsed.",  "status": 400,  "detail": "…"}

Returned by

• Validate a Peppol document POST /v1/validations
• Convert a JSON invoice to Peppol UBL POST /v1/conversions
• Email a one-time sign-in code POST /v1/sign-ins
• Exchange a one-time code for an API key POST /v1/sign-ins/{sign_in_id}/confirmation
• Create an API key POST /v1/keys
• Start a subscription POST /v1/billing/checkout-sessions