Invalid Request Format
This error occurs when the API client sends a payload that cannot be parsed by the server, typically due to malformed JSON.
Error Response Example (RFC 9457)
Section titled “Error Response Example (RFC 9457)”{ "type": "https://docs.apinow.app/errors/invalid-request-format", "title": "Invalid Request Format", "status": 400, "code": "INVALID_REQUEST_FORMAT", "detail": "Unexpected token } in JSON at position 42", "instance": "/api/v1/users"}Troubleshooting Guide
Section titled “Troubleshooting Guide”For API Consumers (What it means & how to fix)
Section titled “For API Consumers (What it means & how to fix)”- Malformed JSON Syntax: Check that your JSON payload is formatted correctly. Common issues include:
- Mismatched or missing closing brackets (
},]). - Missing commas between fields.
- Trailing commas after the last property.
- Single quotes (
') instead of double quotes (") around strings or keys.
- Mismatched or missing closing brackets (
- Incorrect Content-Type Header: Ensure your request includes the header
Content-Type: application/json.
For API Authors (Domain & API Modeler notes)
Section titled “For API Authors (Domain & API Modeler notes)”- This is a client-side syntax error. The API Modeler and Domain Modeler are correctly configured, but the client application is sending raw request bodies that violate standard JSON syntax.