The 'Invalid JSON in request body' error from Claude's API means your request payload contains malformed JSON that cannot be parsed. Common causes include unescaped special characters, trailing commas, single quotes instead of double quotes, or template strings that broke the JSON structure. Validate your JSON before sending and use SDK methods instead of raw HTTP calls.
What does "Invalid JSON in request body" mean in Claude?
When the Claude API returns "Invalid JSON in request body" (HTTP 400), it means the server could not parse the JSON you sent. The API expects every request body to be valid JSON with proper formatting — double-quoted strings, no trailing commas, no comments, and properly escaped special characters. This is a client-side error: your code is sending something that is not valid JSON.
The Anthropic API returns this as an invalid_request_error type with a descriptive message. Variants include "Invalid or malformed JSON" and "Could not parse request body as JSON." The error response itself is valid JSON containing the error details, which confirms the server is reachable — it just cannot understand what you sent.
This error appears most often when developers build request bodies using string concatenation or template literals instead of using JSON.stringify() or the SDK's built-in methods. It also occurs when user input containing special characters (newlines, tabs, quotes, backslashes) is injected directly into the JSON without escaping.
Common causes
User input containing unescaped newlines, tabs, quotes, or
backslashes is injected directly into the JSON request body
String concatenation or template literals are
used to build the JSON payload instead of JSON.stringify() or equivalent serialization
The request body contains trailing commas, single quotes, or
JavaScript-style comments that are valid in JS but invalid in JSON
A Content-Type header is missing or
set incorrectly (should be application/json), causing the server to misinterpret the body
Character encoding issues where non-UTF-8 characters or
byte-order marks corrupt the JSON structure
An empty or truncated request body is
sent due to a middleware or proxy stripping the body content before it reaches the API
How to fix "Invalid JSON in request body" in Claude
The simplest and most reliable fix is to use the official Anthropic SDK instead of making raw HTTP requests. The SDK handles all JSON serialization, escaping, and header configuration automatically, eliminating this entire class of errors.
If you must use raw HTTP requests, always use your language's built-in JSON serialization (JSON.stringify in JavaScript, json.dumps in Python, json.Marshal in Go) instead of building JSON strings manually. Never concatenate user input into JSON templates.
To debug the issue, log the exact request body being sent and validate it at jsonlint.com or with a local JSON parser. Common problems include: newline characters in user messages (must be escaped as \n in JSON), literal tab characters (must be \t), and unescaped double quotes inside strings (must be \"). Make sure the Content-Type header is set to application/json.
For complex prompts with code blocks, multiline text, or special characters, always serialize through your language's JSON library. This is especially important when the content field includes code snippets that contain their own quotes, braces, or escape sequences.
import requests# BAD: String concatenation with unescaped user inputuser_msg = 'Explain what "hello world" means'body = '{"model": "claude-sonnet-4-20250514", "max_tokens": 1024, "messages": [{"role": "user", "content": "' + user_msg + '"}]}'response = requests.post( "https://api.anthropic.com/v1/messages", headers={"x-api-key": api_key, "anthropic-version": "2023-06-01"}, data=body)import anthropic# GOOD: Use the SDK — handles all serialization automaticallyclient = anthropic.Anthropic()user_msg = 'Explain what "hello world" means'response = client.messages.create( model="claude-sonnet-4-20250514", max_tokens=1024, messages=[{"role": "user", "content": user_msg}])# If you must use raw HTTP, use json parameter (not data)import requests, jsonresponse = requests.post( "https://api.anthropic.com/v1/messages", headers={ "x-api-key": api_key, "anthropic-version": "2023-06-01", "content-type": "application/json" }, json={ # requests library auto-serializes this "model": "claude-sonnet-4-20250514", "max_tokens": 1024, "messages": [{"role": "user", "content": user_msg}] })Prevention tips
- Always use the official Anthropic SDK instead of raw HTTP requests — it handles JSON serialization, escaping, and headers automatically
- If using raw HTTP, pass a dictionary to the json parameter (not data) in your HTTP library, which handles serialization and Content-Type headers
- Log the exact request body before sending and validate it at jsonlint.com to catch malformed JSON before it hits the API
- Sanitize and escape user-provided input before including it in API requests, especially content containing code snippets, quotes, or newlines
Still stuck?
Copy one of these prompts to get a personalized, step-by-step explanation.
I'm getting 'Invalid JSON in request body' from the Claude/Anthropic API. I'm building the request using string templates in Python. The user input may contain quotes and newlines. How do I properly serialize the request body?
My Claude API call returns 'Invalid JSON in request body'. Here is my request code: [paste code]. Identify why the JSON is malformed and fix it using proper serialization.
Frequently asked questions
What causes "Invalid JSON in request body" in the Claude API?
The most common cause is building JSON using string concatenation instead of a proper JSON serializer. When user input contains special characters like quotes, newlines, or backslashes, these break the JSON structure. Always use JSON.stringify() in JavaScript or json.dumps() in Python to serialize your request body.
How do I debug a malformed JSON error in Claude?
Log the exact request body string your code generates, then paste it into a JSON validator like jsonlint.com. The validator will pinpoint the exact character position where the JSON breaks. Common issues include unescaped quotes, trailing commas, and literal newline characters.
Does the Anthropic SDK prevent "Invalid JSON in request body" errors?
Yes. The official Python and TypeScript SDKs handle all JSON serialization internally, so you pass native objects (dictionaries, arrays) and the SDK converts them to valid JSON. This eliminates manual serialization errors entirely.
Can special characters in my prompt cause this JSON error?
Yes. Characters like double quotes, backslashes, newlines, and tabs have special meaning in JSON and must be escaped. If you inject raw user input into a JSON string without escaping, these characters will break the JSON structure. Use your language's JSON serializer to handle escaping automatically.
Why do I get this error only with certain user inputs?
If you are building JSON with string concatenation, the error only appears when user input contains characters that break JSON syntax. Simple text works fine, but input with quotes, newlines, code snippets, or unicode characters will corrupt the JSON. Switch to proper serialization to handle all inputs safely.
Can RapidDev help fix JSON serialization issues in my Claude integration?
Yes. RapidDev can refactor your API integration to use the official SDK with proper error handling, ensuring all inputs are safely serialized regardless of content. This eliminates JSON parsing errors and improves the reliability of your Claude-powered application.
Talk to an Expert
Our team has built 600+ apps. Get personalized help with your issue.
Book a free consultation