Skip to content
Last updated

Bad Request

HTTP Status: 400 Bad Request
RFC Reference: RFC 9110 Section 15.5.1

The request is malformed or contains invalid syntax.

Response

{
  "type": "https://docs.apiera.io/problems/bad-request",
  "title": "Bad Request",
  "status": 400,
  "detail": "The request could not be understood by the server due to malformed syntax.",
  "instance": "/v1/products",
  "correlationId": "550e8400-e29b-41d4-a716-446655440000"
}

Common Causes

  • Invalid JSON syntax
  • Missing required headers
  • Malformed request parameters
  • Invalid data types

How to Fix

  • Validate JSON syntax
  • Ensure all required headers are present
  • Check parameter formats match API specification
  • Verify Content-Type header is correct