---
title: "Bad Request"
description: "The server could not read the request: malformed JSON, a badly percent-encoded path, an incomplete body or too much nesting. Fix the request and retry."
canonical: "https://signatureapi.com/docs/v1/errors/bad-request"
source: "https://signatureapi.com/docs/v1/errors/bad-request.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T11:41:57Z"
---

# Bad Request

The server could not read the request: malformed JSON, a badly percent-encoded path, an incomplete body or too much nesting. Fix the request and retry.

_Last verified against API version 1.18.0._

## What Happened

The server could not read the request. The `detail` property says which of these applies:

- The request body is not valid JSON.
- The request path is not validly percent-encoded.
- The request body does not match its `Content-Length` header, or was not received completely.
- The request body is nested too deeply.

## Example response

```json 400 Bad Request (application/problem+json)
{
  "type": "https://signatureapi.com/docs/v1/errors/bad-request",
  "title": "Bad Request",
  "status": 400,
  "detail": "The request body is not valid JSON."
}
```

## How to Fix

- Check that the JSON is valid: double-quoted keys and strings, braces `{}` for objects, brackets `[]` for arrays, no trailing commas.
- Percent-encode special characters in the request path, such as a space as `%20`. A `%` must be followed by two hexadecimal digits.
- Let your HTTP client set the `Content-Length` header, and retry if the connection was interrupted.
- Reduce the nesting depth of the request body.

Still stuck? [Contact support](https://signatureapi.com/support).
