HTTP 400 Bad Request — What It Means

chain

HTTP 400 Bad Request — what does HTTP 400 mean?

runs in your browser

⌃⏎ run · ⎋ clear · / focus input

Status code

Meaning

send output to

no matches

Result appears here as you type

runs in your browser · nothing uploaded

HTTP 400 Bad Request Online

Updated 2026-07-26

HTTP 400 Bad Request means the server couldn't even parse your request properly — malformed JSON, a missing required parameter, or syntax that doesn't match what the endpoint expects. It's a structural problem with the request itself, caught before any real processing begins.

Start by checking the exact shape of what's being sent: valid JSON (no trailing commas, properly escaped strings), the right Content-Type header for the body format, and correctly URL-encoded query parameters. If the request parses fine but a specific field fails a business rule, that's 422 Unprocessable Entity instead. For every other status code at once, use the full HTTP Status Codes reference.

// how to use

1 The code is already looked up below — 400 is pre-filled.
2 Type any other status code to look that one up instead.
3 Copy the result, or use the full HTTP Status Codes reference for every code at once.

// examples

The code itself

Input

Output

400 Bad Request — Client Error (4xx). The server cannot process the request due to a client error.

A code it's easy to confuse with

Input

Output

422 Unprocessable Entity — the request is well-formed, but the data inside it fails validation.

// common uses

Debugging malformed JSON or query parameters in an API request Distinguishing a structurally broken request (400) from a validation failure (422) Explaining a 400 in API integration documentation Checking what a status code in server logs actually means

// faq

Is anything uploaded to a server?

No. The lookup runs entirely in your browser from a built-in table, so nothing you type leaves your machine.

What actually triggers a 400?

Malformed request syntax — invalid JSON in the body, a missing required parameter, a query string the server can't parse, or a request that violates the API's basic structural expectations before any business-logic validation even runs.

How is 400 different from 422 Unprocessable Entity?

400 means the request itself is broken — bad JSON, wrong content type, malformed syntax. 422 means the request is perfectly well-formed but the DATA inside it fails a validation rule (like a required field being empty or an email being invalid).

My request body looks fine — why is it still 400?

Common culprits are a trailing comma or unescaped quote in JSON, sending form-encoded data with a JSON Content-Type header (or vice versa), or a query parameter that isn't URL-encoded correctly.

Is a 400 the client's fault or the server's?

The client's — 400 is explicitly a 4xx client error, meaning the request as sent doesn't meet the server's basic requirements. Fixing it means fixing what's being sent, not the server.

// works with your data

Sort & Dedupe Lines Slug Generator Reverse Text Text Repeater Remove Duplicate Lines Whitespace Remover

Use this via API

Get a free API key →

curl -X POST https://thesnaptools.com/api/v1/tools/http-400 \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"400"}'