JSON validation errors occur when JSON text cannot be parsed, when parsed JSON does not satisfy a schema, or when an API or application rejects otherwise valid JSON because it violates its contract or business rules. The first step is to determine which layer failed: syntax, schema, or application validation.

Quick Steps

1
Capture the exact JSON that failed.
2
Check whether the text is valid JSON syntax.
3
Read the parser error and inspect the reported location.
4
If syntax is valid, validate the JSON against the expected schema.
5
Check required fields, data types, arrays, enums, and nested objects.
6
If schema validation passes, inspect the API response, authentication, permissions, and application-specific rules.
7
Fix the actual failing layer and validate again.

JSON Validation Errors: How to Diagnose and Fix JSON Problems

A JSON validation error doesn't always mean the same thing. A parser can reject malformed JSON syntax, a JSON Schema validator can reject a structurally incorrect object, or an API can reject valid JSON because it doesn't satisfy the endpoint's contract. Treating all three as the same problem makes debugging harder. This guide breaks JSON validation failures into these layers and shows how to identify, understand, and fix each type.

What Is a JSON Validation Error?

A JSON validation error is a failure reported when JSON data does not satisfy the rules expected by the parser, schema, API, or application processing it. The important detail is that the word validation can refer to different checks. A syntax error means the text is not valid JSON. A schema error means the parsed JSON does not match an expected structure. An API validation error can involve additional contract or business rules.

The Three Main Layers of JSON Validation

Before fixing an error, identify which layer rejected the data.

JSON syntax

"Can this text be parsed as JSON?"

Missing comma
Trailing comma
Unmatched bracket
Missing colon
Single quotes
Invalid escape sequence

Schema validation

"Does the parsed JSON match the expected structure?"

Missing required property
Wrong data type
Invalid enum value
Incorrect array items
Unexpected property

Application or API validation

"Does the data satisfy the endpoint or application's rules?"

Invalid business state
Unauthorized operation
Invalid identifier
Authentication failure
Application-specific constraints

JSON syntax

Can this text be parsed as JSON?

Schema validation

Does the parsed JSON match the expected structure?

Application or API validation

Does the data satisfy the endpoint or application's rules?

JSON Syntax Errors vs Validation Errors

Strictly speaking, malformed JSON syntax is a parsing problem rather than a schema-validation failure. For example, a missing comma prevents the JSON text from being parsed into a JSON value. Once parsing succeeds, schema or application validation can operate on the resulting data.

Common JSON Validation Errors

The exact wording varies by parser and validation library, but the underlying problems tend to repeat.

Unexpected tokenSyntax

Cause: A character or token is not valid at the current position.

Action: Inspect the reported location and the preceding token.

Unexpected end of JSON inputSyntax

Cause: The document ended before the JSON structure was complete.

Action: Check closing braces, brackets, and incomplete strings.

Expected comma or closing braceSyntax

Cause: An object member is missing a separator or closing delimiter.

Action: Check the previous property for a missing comma.

Required property missingSchema

Cause: A required field is absent.

Action: Add the required property or confirm whether the schema is correct.

Invalid typeSchema

Cause: The value has a different type from the schema requirement.

Action: Check whether the API expects a string, number, boolean, array, object, or null.

Value not allowedSchema

Cause: A value does not satisfy an enum, const, range, pattern, or other constraint.

Action: Compare the value with the schema constraint.

Additional property not allowedSchema

Cause: The object contains a property that the schema does not permit under its configured rules.

Action: Remove the property or update the schema if the field is intentional.

Invalid request bodyAPI

Cause: The server could not accept the submitted JSON according to the endpoint contract.

Action: Inspect the API documentation, status code, response body, and expected request schema.

Unexpected token

Cause: A character or token is not valid at the current position.

Inspect the reported location and the preceding token.

Unexpected end of JSON input

Cause: The document ended before the JSON structure was complete.

Check closing braces, brackets, and incomplete strings.

Expected comma or closing brace

Cause: An object member is missing a separator or closing delimiter.

Check the previous property for a missing comma.

Required property missing

Cause: A required field is absent.

Add the required property or confirm whether the schema is correct.

Invalid type

Cause: The value has a different type from the schema requirement.

Check whether the API expects a string, number, boolean, array, object, or null.

Value not allowed

Cause: A value does not satisfy an enum, const, range, pattern, or other constraint.

Compare the value with the schema constraint.

Additional property not allowed

Cause: The object contains a property that the schema does not permit under its configured rules.

Remove the property or update the schema if the field is intentional.

Invalid request body

Cause: The server could not accept the submitted JSON according to the endpoint contract.

Inspect the API documentation, status code, response body, and expected request schema.

Unexpected Token JSON Error

An unexpected-token error usually means the parser encountered something that cannot occur at the current point in the JSON grammar. The token might be a quote, comma, bracket, letter, or other character. The reported location is where the parser detected the problem, so the original mistake may be immediately before it.

When the error points at age, inspect the end of the previous name property first. The missing comma is the actual syntax problem.

Missing commajson

{
  "name": "Ramesh"
  "age": 30
}

Unexpected End of JSON Input

This error commonly occurs when JSON ends before an object, array, or string has been completed.

Missing closing bracejson

{
  "name": "Ramesh",
  "active": true

Complete JSONjson

{
  "name": "Ramesh",
  "active": true
}

Missing Comma Validation Error

Object members and array elements need commas between adjacent values. A missing comma is especially easy to miss in manually edited configuration files or generated JSON.

json

{
  "name": "Ramesh",
  "role": "developer"
  "active": true
}

json

{
  "name": "Ramesh",
  "role": "developer",
  "active": true
}

Trailing Comma Validation Error

Standard JSON does not permit a trailing comma after the final object member or array element.

Invalidjson

{
  "name": "Ramesh",
  "active": true,
}

Validjson

{
  "name": "Ramesh",
  "active": true
}

Quote and String Validation Errors

JSON strings use double quotation marks. Incorrect quotes, unescaped quotation marks, and invalid escape sequences can prevent parsing.

Invalid quotesjson

{'name': 'Ramesh'}

Valid JSONjson

{"name": "Ramesh"}

Invalid JSON Values

JSON has a defined set of value types. JavaScript-specific values such as undefined, NaN, and Infinity are not standard JSON values.

Valid Values

string
number
object
array
true
false
null

Invalid Examples

undefined
NaN
Infinity

Missing Required Property Error

A schema can require certain properties to be present. If the JSON parses correctly but omits a required property, syntax checking succeeds while schema validation fails.

The JSON is syntactically valid. It fails only if the schema requires a name property.

Schema requires namejson

{
  "active": true
}

The JSON is syntactically valid. It fails only if the schema requires a name property.

Invalid JSON Data Type Error

Schema validation can require a specific JSON type. A value that looks reasonable to a human can still be rejected if its type does not match the contract.

The first example is valid JSON. It is a validation error only when the schema or application expects age to be a number.

Number expectedjson

{
  "age": "30"
}

Number providedjson

{
  "age": 30
}

The first example is valid JSON. It is a validation error only when the schema or application expects age to be a number.

Invalid Enum Value

An enum constraint limits a property to a defined set of values. A JSON string can be syntactically valid while still failing because its value is not one of the permitted choices.

If the schema permits only active and inactive, pending fails schema validation even though the JSON syntax is correct.

Example enumjson

{
  "status": "pending"
}

If the schema permits only active and inactive, pending fails schema validation even though the JSON syntax is correct.

Array Validation Errors

Schemas can constrain whether a property is an array, what types its items contain, how many items are allowed, and sometimes other properties such as uniqueness.

Is the value actually an array?
Are array items the expected type?
Does the array contain the required number of items?
Are nested objects valid?
Are item values within the allowed constraints?

Is the value actually an array?
Are array items the expected type?
Does the array contain the required number of items?
Are nested objects valid?
Are item values within the allowed constraints?

Nested Object Validation Errors

A top-level object can be valid while a deeply nested property violates the schema. When validation errors identify a property path, follow that path through each nested object or array.

Start at the reported property path rather than scanning the entire document.

user.profile.address.postalCode

String Length, Pattern, and Format Errors

Schema validation can impose additional constraints on strings. Depending on the schema and validator, a string may fail because it is too short, too long, does not match a regular-expression pattern, or does not satisfy a declared format or application-specific rule.

Minimum length
Maximum length
Pattern
Format
Allowed values
Constant value

Minimum length
Maximum length
Pattern
Format
Allowed values
Constant value

Number Range Validation Errors

A number can be valid JSON but still fail schema validation when it falls outside an allowed range.

minimum
maximum
exclusiveMinimum
exclusiveMaximum
multipleOf

minimum
maximum
exclusiveMinimum
exclusiveMaximum
multipleOf

Null vs Missing Property

A property being absent is not automatically the same as the property being present with a null value. Whether null is allowed depends on the schema or application's rules.

Optional and nullable are different concepts. A field can be optional but reject null, or required while allowing null, depending on the rules.

Missing propertyjson

{}

Explicit nulljson

{
  "middleName": null
}

Optional and nullable are different concepts. A field can be optional but reject null, or required while allowing null, depending on the rules.

Additional Property Validation Errors

Some schemas or API contracts restrict which object properties are accepted. An unexpected property may therefore cause validation to fail. Whether unknown properties are rejected, ignored, or preserved depends on the schema and application.

JSON Schema Validation Errors

A JSON Schema validator compares a parsed JSON instance against constraints defined by a schema. A useful validation error should identify the failing location and explain which constraint was violated. The exact error structure depends on the validator and JSON Schema dialect.

Example JSON Schema Validation Failure

Consider an object where name must be a string and age must be an integer.

The instance is valid JSON, but age has the wrong type for the schema.

Schemajson

{
  "type": "object",
  "required": ["name", "age"],
  "properties": {
    "name": { "type": "string" },
    "age": { "type": "integer" }
  }
}

Invalid instancejson

{
  "name": "Ramesh",
  "age": "30"
}

The instance is valid JSON, but age has the wrong type for the schema.

How to Read JSON Validation Error Paths

Validation libraries often report a path into the JSON document. The path tells you which property or array item failed. A path such as user.profile.email points to the email property nested inside profile inside user.

How to Fix JSON Validation Errors

The fix depends on which validation layer failed. Do not change the schema simply to make an error disappear unless the schema itself is incorrect.

Identify the validation layer.
Capture the exact input.
Read the full error message.
Locate the reported property or token.
Compare the value with the expected syntax or schema.
Make the smallest appropriate correction.
Run syntax validation again.
Run schema validation again if applicable.
Retest the API or application workflow.

How to Check JSON Before Schema Validation

Raw JSON text must normally be parsed before a schema validator can evaluate the resulting JSON value. If parsing fails, fix the JSON syntax first.

javascript

let data;

try {
  data = JSON.parse(jsonText);
} catch (error) {
  console.error("Invalid JSON:", error.message);
  throw error;
}

// Validate `data` against a JSON Schema here.

Check JSON Syntax in JavaScript

Use JSON.parse() inside try/catch when JSON arrives as text.

javascript

try {
  const data = JSON.parse(jsonText);
  console.log("Valid JSON syntax");
} catch (error) {
  console.error("JSON syntax error:", error.message);
}

Check JSON Syntax in Python

Python's json.loads() raises JSONDecodeError when JSON text cannot be parsed.

python

import json

try:
    data = json.loads(json_text)
    print("Valid JSON syntax")
except json.JSONDecodeError as error:
    print("Invalid JSON")
    print(error.msg)
    print(error.lineno, error.colno)

Validate JSON with a JSON Schema

Once JSON syntax is valid, use a JSON Schema implementation to test structural constraints. The exact API depends on the programming language and validation library.

1
Parse JSON text.
2
Load the expected JSON Schema.
3
Pass the parsed JSON instance to a schema validator.
4
Inspect validation errors.
5
Correct the instance or schema as appropriate.
6
Run validation again.

JSON API Validation Errors

APIs often validate incoming JSON request bodies against endpoint-specific requirements. An API can return a 4xx response even when the request body is perfectly valid JSON. Check the HTTP status code, response body, API documentation, Content-Type, required fields, data types, authentication, and endpoint-specific rules.

JSON Request Body Validation Errors

For request payloads, separate client-side syntax problems from server-side validation problems. A malformed request cannot be parsed correctly, while a valid request can still fail because a required field is missing or a value is not accepted by the endpoint.

JSON Response Validation Errors

Client applications can also validate API responses. If parsing fails, inspect the raw response. If parsing succeeds but response validation fails, compare the received structure against the documented response schema or application model.

Webhook JSON Validation Errors

Webhook consumers should distinguish JSON parsing from event validation and security verification. A valid JSON body can still be an invalid event for the expected webhook type. Signature verification is a separate security step and may require the original raw request bytes.

/guides/format-webhook-json

JSON Validation Errors in Generated Data

Generated JSON can fail validation even when the generator produces syntactically correct JSON. Common causes include missing fields, inconsistent types, incorrect enum values, unexpected nesting, or values that do not satisfy the target schema. Validate generated data before passing it to downstream systems.

JSON Validation Errors from AI-Generated Data

AI-generated structured output can be valid JSON while still violating an expected schema. Treat generated JSON as untrusted input: parse it, validate its structure, and apply application-level checks before using it in a workflow.

JSON Validation Errors in Configuration Files

Configuration files may use JSON, JSONC, or another JSON-like format. A strict JSON validator can reject comments or other extensions that a particular configuration parser supports. Confirm the exact format before diagnosing the error as invalid configuration.

Why Valid JSON Still Produces a Validation Error

Valid JSON only proves that the text conforms to JSON syntax. It does not prove that the data satisfies a schema, API contract, database constraint, authorization rule, or business requirement. This distinction is one of the most important concepts when debugging JSON validation.

Formatting vs JSON Validation

Formatting makes JSON easier to read by adding indentation and line breaks. Validation checks whether the data satisfies a set of rules. Formatting can help you inspect a document, but it does not replace validation.

JSON Validation vs JSON Repair

Validation identifies whether input satisfies a rule set. Repair attempts to correct malformed input. A validator should not silently rewrite data just because the data fails validation. If the intended correction is ambiguous, the original input should be preserved for review.

/guides/fix-invalid-json

Using JSON Validation in CI

Projects can validate JSON fixtures, configuration files, schemas, and API examples during continuous integration. This catches malformed or structurally incorrect data before it reaches production.

Parse JSON fixtures.
Validate important fixtures against schemas.
Validate API contract examples.
Test representative invalid inputs.
Fail the build when required validation fails.

Parse JSON fixtures.
Validate important fixtures against schemas.
Validate API contract examples.
Test representative invalid inputs.
Fail the build when required validation fails.

JSON Validation Errors in Tests

Automated tests should cover both valid and invalid JSON cases. Testing only successful examples makes it difficult to detect regressions in error handling. Include malformed syntax, missing fields, wrong types, invalid enum values, boundary values, and unexpected structures where they matter.

Handling Validation Errors in Production

Production systems should return useful errors without exposing secrets or internal implementation details. Client-facing errors can identify the invalid field and expected type or constraint, while detailed internal logs can retain diagnostic context subject to the application's security and privacy requirements.

Return structured error responses.
Identify the failing field when appropriate.
Avoid exposing credentials or tokens.
Avoid logging entire sensitive payloads unnecessarily.
Use stable error codes for client integrations.
Keep internal stack traces out of public API responses.

Return structured error responses.
Identify the failing field when appropriate.
Avoid exposing credentials or tokens.
Avoid logging entire sensitive payloads unnecessarily.
Use stable error codes for client integrations.
Keep internal stack traces out of public API responses.

Sensitive Data and JSON Validation

JSON validation often happens on data containing access tokens, passwords, personal information, or internal identifiers. Do not paste sensitive production payloads into an external validator without understanding how the service handles submitted data. Redact secrets when practical or validate locally.

Large JSON Validation Errors

Large documents can make manual debugging difficult. Use validators that report precise paths or positions, pretty print valid data for inspection, and isolate the smallest failing object or array when possible. For very large datasets, streaming or incremental processing may be more appropriate than loading the entire document into memory.

A Layered JSON Validation Workflow

A reliable workflow separates parsing from structure and application logic.

Receive or generate the JSON.
Preserve the original input when debugging.
Parse the JSON text.
Fix syntax errors if parsing fails.
Pretty print the successfully parsed data when inspection is useful.
Validate the parsed value against the expected schema.
Inspect the exact failing property path.
Fix missing fields, types, values, or structural issues.
Apply application and business validation.
Send or process the data.
Log safe diagnostic information if the operation fails.
Retest with both valid and invalid examples.

Common Mistakes When Debugging JSON Validation

Several debugging habits make JSON validation failures harder to diagnose.

Calling every JSON error a syntax error.
Changing the schema before checking the input.
Assuming valid JSON means valid API data.
Ignoring the reported property path.
Treating null and missing as identical.
Assuming a number represented as a string is automatically equivalent to a number.
Using JavaScript object syntax as if it were JSON.
Ignoring API status codes.
Formatting sensitive production data through unknown external services.
Silently repairing malformed JSON without reviewing the result.

Calling every JSON error a syntax error.
Changing the schema before checking the input.
Assuming valid JSON means valid API data.
Ignoring the reported property path.
Treating null and missing as identical.
Assuming a number represented as a string is automatically equivalent to a number.
Using JavaScript object syntax as if it were JSON.
Ignoring API status codes.
Formatting sensitive production data through unknown external services.
Silently repairing malformed JSON without reviewing the result.

Best Practices for JSON Validation Errors

Good validation design makes failures easy to diagnose while keeping data and system details protected.

Validate syntax at input boundaries.
Use JSON Schema for reusable structural rules.
Keep business rules separate from basic JSON syntax.
Return field-level errors when practical.
Use stable machine-readable error codes for APIs.
Include precise property paths in validation diagnostics.
Distinguish missing, null, and wrong-type values.
Test boundary conditions and invalid inputs.
Keep schemas and API contracts versioned.
Do not expose secrets in validation messages.
Validate generated and externally supplied JSON before downstream processing.
Document whether unknown properties are accepted or rejected.

Validate syntax at input boundaries.
Use JSON Schema for reusable structural rules.
Keep business rules separate from basic JSON syntax.
Return field-level errors when practical.
Use stable machine-readable error codes for APIs.
Include precise property paths in validation diagnostics.
Distinguish missing, null, and wrong-type values.
Test boundary conditions and invalid inputs.
Keep schemas and API contracts versioned.
Do not expose secrets in validation messages.
Validate generated and externally supplied JSON before downstream processing.
Document whether unknown properties are accepted or rejected.

JSON Formatting Examples

Basic JavaScript JSON Validation

javascript

function parseJSON(text) {
  try {
    return {
      valid: true,
      data: JSON.parse(text)
    };
  } catch (error) {
    return {
      valid: false,
      error: error.message
    };
  }
}

Python JSON Validation

python

import json

def parse_json(text):
    try:
        return json.loads(text)
    except json.JSONDecodeError as error:
        raise ValueError(
            f"Invalid JSON at line {error.lineno}, column {error.colno}: {error.msg}"
        ) from error

Parse Before Schema Validation

javascript

let data;

try {
  data = JSON.parse(jsonText);
} catch (error) {
  throw new Error(`Invalid JSON: ${error.message}`);
}

// Pass `data` to your JSON Schema validator here.

Pretty Print After Successful Parsing

javascript

const data = JSON.parse(jsonText);
const formatted = JSON.stringify(data, null, 2);
console.log(formatted);

Validate JSON from the Command Line

bash

jq . data.json

JSON Validation Error Checklist

Capture the exact JSON that failed.
Determine whether the input is standard JSON or a JSON-like format.
Run a syntax check first.
Read the parser error and location.
Check commas, quotes, colons, braces, and brackets.
Check JSON values and escape sequences.
Confirm that parsing succeeds.
Identify the expected JSON Schema or API contract.
Check required properties.
Check property data types.
Check enum and constant values.
Check arrays and nested objects.
Check string constraints.
Check number ranges.
Distinguish missing properties from null values.
Check unknown or additional properties.
Follow the reported property path.
Check the API status code and response body.
Separate schema errors from business-rule errors.
Retest after the correction.
Test both valid and invalid cases.
Avoid exposing sensitive JSON in logs.
Prefer local validation for sensitive production data.

Frequently Asked Questions

Q:What is a JSON validation error?

It is a failure reported when JSON data does not satisfy the syntax, schema, API contract, or application rules being checked.

Q:Why is my JSON validation failing?

First determine whether the failure is a parsing error, schema error, or application/API error. The fix depends on which layer rejected the data.

Q:What is the difference between a JSON syntax error and a validation error?

A syntax error means the JSON text cannot be parsed. A broader validation error can also mean that valid JSON fails a schema or application rule.

Q:What does unexpected token mean in JSON?

It means the parser encountered a character or token that is not valid at that position. The actual mistake may be immediately before the reported location.

Q:What does unexpected end of JSON input mean?

The JSON ended before the parser found the closing structure or completed value it expected. Missing braces, brackets, or quotation marks are common causes.

Q:How do I fix a JSON validation error?

Identify the failing layer, read the error location or property path, compare the input with the expected syntax or schema, make the appropriate correction, and validate again.

Q:Can valid JSON fail validation?

Yes. Valid JSON can fail JSON Schema validation or an API's contract because required fields, types, values, or structural requirements are not satisfied.

Q:Can valid JSON be rejected by an API?

Yes. APIs can reject syntactically valid JSON because of missing fields, incorrect types, invalid values, authentication, authorization, or business rules.

Q:What causes a missing required property error?

The JSON instance does not contain a property that the schema or API contract requires.

Q:What causes an invalid type error?

The value's JSON type does not match the expected type. For example, a schema may require a number while the input contains a string.

Q:Is a number stored as a string a JSON error?

No. A quoted number such as "30" is valid JSON. It becomes a validation error only when the schema or application expects a numeric value.

Q:What causes an enum validation error?

The value is not one of the values permitted by the schema or API contract.

Q:What causes an array validation error?

The value may not be an array, its items may have incorrect types, its length may violate constraints, or nested items may fail their own validation rules.

Q:What is a JSON Schema validation error?

It means a parsed JSON instance failed one or more constraints defined by a JSON Schema.

Q:Does JSON Schema validate JSON syntax?

Schema validation operates on a JSON instance, so the JSON text normally needs to parse successfully first. Syntax checking and schema validation are separate stages.

Q:Why does the JSON error point to the wrong line?

A parser reports where it detected that parsing could not continue. The actual mistake, such as a missing comma, can occur on the preceding line.

Q:How do I find which JSON field caused validation to fail?

Use the validation error's property path when the validator provides one. Paths such as user.profile.email identify the nested field that violated a rule.

Q:What does a JSON validation path mean?

It identifies the location of the failing value inside the JSON structure, including nested properties and array indexes.

Q:What is the difference between null and a missing JSON property?

A missing property is absent, while null is an explicit JSON value. A schema can treat them differently.

Q:Can optional JSON fields contain null?

Not necessarily. Optional means the property may be absent. Nullable means null is an accepted value. The schema or application must define whether null is allowed.

Q:What causes an additional property validation error?

The JSON object contains a property that the schema or API contract does not permit under its configured rules.

Q:Can comments cause JSON validation errors?

Yes. Standard JSON does not support comments. A strict parser can reject comments even if a JSON-like configuration format accepts them.

Q:Can trailing commas cause JSON validation errors?

Yes. Standard JSON does not allow trailing commas in objects or arrays.

Q:Can single quotes cause JSON validation errors?

Yes. Standard JSON uses double quotes for strings and object property names.

Q:Can formatting fix JSON validation errors?

Formatting improves readability but does not normally repair invalid syntax or make a schema-invalid value conform to the schema.

Q:Should I format JSON before validating it?

You can format successfully parsed JSON to make it easier to inspect. If the input is malformed, fix the parsing problem first.

Q:How do I validate JSON in JavaScript?

Use JSON.parse() to check syntax, then pass the resulting value to a JSON Schema validator when structural validation is required.

Q:How do I validate JSON in Python?

Use json.loads() for JSON text or json.load() for files, then use an appropriate schema-validation library when structural validation is required.

Q:How do I validate JSON from the command line?

Tools such as jq can parse JSON and report syntax errors. Schema validation requires a tool that supports the relevant JSON Schema dialect.

Q:Why does generated JSON pass syntax validation but fail schema validation?

A generator can produce syntactically correct JSON while omitting required properties, using incorrect types, choosing unsupported values, or producing the wrong structure.

Q:Can AI-generated JSON have validation errors?

Yes. AI-generated output can be valid JSON while still violating a required schema or application contract. Treat generated structured data as untrusted until it has been validated.

Q:How do I handle JSON validation errors in an API?

Return structured errors that identify the failing field or constraint when appropriate, use stable error codes, and avoid exposing credentials or internal implementation details.

Q:Should JSON validation happen on the client or server?

Client-side validation can improve user feedback, but server-side validation is still required when the server accepts untrusted input.

Q:Should I validate JSON before sending an API request?

Yes. Check syntax first and validate against the known request contract when practical. The server should still perform its own validation.

Q:Should I validate an API response?

For important integrations, response validation can detect unexpected changes or malformed data before it reaches application logic.

Q:How should I handle validation errors containing sensitive data?

Avoid putting passwords, tokens, personal information, or complete production payloads into error messages and logs unless there is a clear security-controlled reason to do so.

Q:Can a JSON validator repair invalid JSON?

Validation normally reports failures. Repair is a separate operation and any automatic correction should be reviewed before the result is trusted.

Q:What should I do if JSON syntax is valid but validation still fails?

Move to the next layer: compare the parsed JSON with the JSON Schema or API contract, then inspect application-specific rules if the schema passes.

Explore More Resources

JSON Formatter

How to Validate JSON

JSON Validation

JSON Syntax Checker

JSON Syntax

JSON Parse Errors

Fix Invalid JSON

JSON Schema

JSON Schema vs JSON Validation

Read more about JSON Schema vs JSON Validation

JSON Pretty Print

How to Format JSON

JSON Beautifier

JSON Indentation

Format JSON API Response

Read more about Format JSON API Response

Format REST API Response

Read more about Format REST API Response

Format JSON Payload

Format Webhook JSON

Debug JSON API Response

JSON Formatting vs Minification

Read more about JSON Formatting vs Minification

JSON Minifier

JSON Validation Errors

Understand why JSON validation fails, identify the exact layer causing the problem, and fix syntax, schema, and API validation errors.

Validate JSON Learn JSON Validation

What causes JSON validation errors?

Quick Steps

1
Capture the exact JSON that failed.
2
Check whether the text is valid JSON syntax.
3
Read the parser error and inspect the reported location.
4
If syntax is valid, validate the JSON against the expected schema.
5
Check required fields, data types, arrays, enums, and nested objects.
6
If schema validation passes, inspect the API response, authentication, permissions, and application-specific rules.
7
Fix the actual failing layer and validate again.

JSON Validation Errors: How to Diagnose and Fix JSON Problems

What Is a JSON Validation Error?

The Three Main Layers of JSON Validation

Before fixing an error, identify which layer rejected the data.

JSON syntax

"Can this text be parsed as JSON?"

Missing comma
Trailing comma
Unmatched bracket
Missing colon
Single quotes
Invalid escape sequence

Schema validation

"Does the parsed JSON match the expected structure?"

Missing required property
Wrong data type
Invalid enum value
Incorrect array items
Unexpected property

Application or API validation

"Does the data satisfy the endpoint or application's rules?"

Invalid business state
Unauthorized operation
Invalid identifier
Authentication failure
Application-specific constraints

JSON syntax

Can this text be parsed as JSON?

Schema validation

Does the parsed JSON match the expected structure?

Application or API validation

Does the data satisfy the endpoint or application's rules?

JSON Syntax Errors vs Validation Errors

Common JSON Validation Errors

The exact wording varies by parser and validation library, but the underlying problems tend to repeat.

Unexpected tokenSyntax

Cause: A character or token is not valid at the current position.

Action: Inspect the reported location and the preceding token.

Unexpected end of JSON inputSyntax

Cause: The document ended before the JSON structure was complete.

Action: Check closing braces, brackets, and incomplete strings.

Expected comma or closing braceSyntax

Cause: An object member is missing a separator or closing delimiter.

Action: Check the previous property for a missing comma.

Required property missingSchema

Cause: A required field is absent.

Action: Add the required property or confirm whether the schema is correct.

Invalid typeSchema

Cause: The value has a different type from the schema requirement.

Action: Check whether the API expects a string, number, boolean, array, object, or null.

Value not allowedSchema

Cause: A value does not satisfy an enum, const, range, pattern, or other constraint.

Action: Compare the value with the schema constraint.

Additional property not allowedSchema

Cause: The object contains a property that the schema does not permit under its configured rules.

Action: Remove the property or update the schema if the field is intentional.

Invalid request bodyAPI

Cause: The server could not accept the submitted JSON according to the endpoint contract.

Action: Inspect the API documentation, status code, response body, and expected request schema.

Unexpected token

Cause: A character or token is not valid at the current position.

Inspect the reported location and the preceding token.

Unexpected end of JSON input

Cause: The document ended before the JSON structure was complete.

Check closing braces, brackets, and incomplete strings.

Expected comma or closing brace

Cause: An object member is missing a separator or closing delimiter.

Check the previous property for a missing comma.

Required property missing

Cause: A required field is absent.

Add the required property or confirm whether the schema is correct.

Invalid type

Cause: The value has a different type from the schema requirement.

Check whether the API expects a string, number, boolean, array, object, or null.

Value not allowed

Cause: A value does not satisfy an enum, const, range, pattern, or other constraint.

Compare the value with the schema constraint.

Additional property not allowed

Cause: The object contains a property that the schema does not permit under its configured rules.

Remove the property or update the schema if the field is intentional.

Invalid request body

Cause: The server could not accept the submitted JSON according to the endpoint contract.

Inspect the API documentation, status code, response body, and expected request schema.

Unexpected Token JSON Error

When the error points at age, inspect the end of the previous name property first. The missing comma is the actual syntax problem.

Missing commajson

{
  "name": "Ramesh"
  "age": 30
}

Unexpected End of JSON Input

This error commonly occurs when JSON ends before an object, array, or string has been completed.

Missing closing bracejson

{
  "name": "Ramesh",
  "active": true

Complete JSONjson

{
  "name": "Ramesh",
  "active": true
}

Missing Comma Validation Error

Object members and array elements need commas between adjacent values. A missing comma is especially easy to miss in manually edited configuration files or generated JSON.

json

{
  "name": "Ramesh",
  "role": "developer"
  "active": true
}

json

{
  "name": "Ramesh",
  "role": "developer",
  "active": true
}

Trailing Comma Validation Error

Standard JSON does not permit a trailing comma after the final object member or array element.

Invalidjson

{
  "name": "Ramesh",
  "active": true,
}

Validjson

{
  "name": "Ramesh",
  "active": true
}

Quote and String Validation Errors

JSON strings use double quotation marks. Incorrect quotes, unescaped quotation marks, and invalid escape sequences can prevent parsing.

Invalid quotesjson

{'name': 'Ramesh'}

Valid JSONjson

{"name": "Ramesh"}

Invalid JSON Values

JSON has a defined set of value types. JavaScript-specific values such as undefined, NaN, and Infinity are not standard JSON values.

Valid Values

string
number
object
array
true
false
null

Invalid Examples

undefined
NaN
Infinity

Missing Required Property Error

A schema can require certain properties to be present. If the JSON parses correctly but omits a required property, syntax checking succeeds while schema validation fails.

The JSON is syntactically valid. It fails only if the schema requires a name property.

Schema requires namejson

{
  "active": true
}

The JSON is syntactically valid. It fails only if the schema requires a name property.

Invalid JSON Data Type Error

Schema validation can require a specific JSON type. A value that looks reasonable to a human can still be rejected if its type does not match the contract.

The first example is valid JSON. It is a validation error only when the schema or application expects age to be a number.

Number expectedjson

{
  "age": "30"
}

Number providedjson

{
  "age": 30
}

The first example is valid JSON. It is a validation error only when the schema or application expects age to be a number.

Invalid Enum Value

An enum constraint limits a property to a defined set of values. A JSON string can be syntactically valid while still failing because its value is not one of the permitted choices.

If the schema permits only active and inactive, pending fails schema validation even though the JSON syntax is correct.

Example enumjson

{
  "status": "pending"
}

If the schema permits only active and inactive, pending fails schema validation even though the JSON syntax is correct.

Array Validation Errors

Schemas can constrain whether a property is an array, what types its items contain, how many items are allowed, and sometimes other properties such as uniqueness.

Is the value actually an array?
Are array items the expected type?
Does the array contain the required number of items?
Are nested objects valid?
Are item values within the allowed constraints?

Is the value actually an array?
Are array items the expected type?
Does the array contain the required number of items?
Are nested objects valid?
Are item values within the allowed constraints?

Nested Object Validation Errors

A top-level object can be valid while a deeply nested property violates the schema. When validation errors identify a property path, follow that path through each nested object or array.

Start at the reported property path rather than scanning the entire document.

user.profile.address.postalCode

String Length, Pattern, and Format Errors

Minimum length
Maximum length
Pattern
Format
Allowed values
Constant value

Minimum length
Maximum length
Pattern
Format
Allowed values
Constant value

Number Range Validation Errors

A number can be valid JSON but still fail schema validation when it falls outside an allowed range.

minimum
maximum
exclusiveMinimum
exclusiveMaximum
multipleOf

minimum
maximum
exclusiveMinimum
exclusiveMaximum
multipleOf

Null vs Missing Property

A property being absent is not automatically the same as the property being present with a null value. Whether null is allowed depends on the schema or application's rules.

Optional and nullable are different concepts. A field can be optional but reject null, or required while allowing null, depending on the rules.

Missing propertyjson

{}

Explicit nulljson

{
  "middleName": null
}

Optional and nullable are different concepts. A field can be optional but reject null, or required while allowing null, depending on the rules.

Additional Property Validation Errors

JSON Schema Validation Errors

Example JSON Schema Validation Failure

Consider an object where name must be a string and age must be an integer.

The instance is valid JSON, but age has the wrong type for the schema.

Schemajson

{
  "type": "object",
  "required": ["name", "age"],
  "properties": {
    "name": { "type": "string" },
    "age": { "type": "integer" }
  }
}

Invalid instancejson

{
  "name": "Ramesh",
  "age": "30"
}

The instance is valid JSON, but age has the wrong type for the schema.

How to Read JSON Validation Error Paths

How to Fix JSON Validation Errors

The fix depends on which validation layer failed. Do not change the schema simply to make an error disappear unless the schema itself is incorrect.

Identify the validation layer.
Capture the exact input.
Read the full error message.
Locate the reported property or token.
Compare the value with the expected syntax or schema.
Make the smallest appropriate correction.
Run syntax validation again.
Run schema validation again if applicable.
Retest the API or application workflow.

How to Check JSON Before Schema Validation

Raw JSON text must normally be parsed before a schema validator can evaluate the resulting JSON value. If parsing fails, fix the JSON syntax first.

javascript

let data;

try {
  data = JSON.parse(jsonText);
} catch (error) {
  console.error("Invalid JSON:", error.message);
  throw error;
}

// Validate `data` against a JSON Schema here.

Check JSON Syntax in JavaScript

Use JSON.parse() inside try/catch when JSON arrives as text.

javascript

try {
  const data = JSON.parse(jsonText);
  console.log("Valid JSON syntax");
} catch (error) {
  console.error("JSON syntax error:", error.message);
}

Check JSON Syntax in Python

Python's json.loads() raises JSONDecodeError when JSON text cannot be parsed.

python

import json

try:
    data = json.loads(json_text)
    print("Valid JSON syntax")
except json.JSONDecodeError as error:
    print("Invalid JSON")
    print(error.msg)
    print(error.lineno, error.colno)

Validate JSON with a JSON Schema

Once JSON syntax is valid, use a JSON Schema implementation to test structural constraints. The exact API depends on the programming language and validation library.

1
Parse JSON text.
2
Load the expected JSON Schema.
3
Pass the parsed JSON instance to a schema validator.
4
Inspect validation errors.
5
Correct the instance or schema as appropriate.
6
Run validation again.

JSON API Validation Errors

JSON Request Body Validation Errors

JSON Response Validation Errors

Webhook JSON Validation Errors

/guides/format-webhook-json

JSON Validation Errors in Generated Data

JSON Validation Errors from AI-Generated Data

JSON Validation Errors in Configuration Files

Why Valid JSON Still Produces a Validation Error

Formatting vs JSON Validation

JSON Validation vs JSON Repair

/guides/fix-invalid-json

Using JSON Validation in CI

Projects can validate JSON fixtures, configuration files, schemas, and API examples during continuous integration. This catches malformed or structurally incorrect data before it reaches production.

Parse JSON fixtures.
Validate important fixtures against schemas.
Validate API contract examples.
Test representative invalid inputs.
Fail the build when required validation fails.

Parse JSON fixtures.
Validate important fixtures against schemas.
Validate API contract examples.
Test representative invalid inputs.
Fail the build when required validation fails.

JSON Validation Errors in Tests

Handling Validation Errors in Production

Return structured error responses.
Identify the failing field when appropriate.
Avoid exposing credentials or tokens.
Avoid logging entire sensitive payloads unnecessarily.
Use stable error codes for client integrations.
Keep internal stack traces out of public API responses.

Return structured error responses.
Identify the failing field when appropriate.
Avoid exposing credentials or tokens.
Avoid logging entire sensitive payloads unnecessarily.
Use stable error codes for client integrations.
Keep internal stack traces out of public API responses.

Sensitive Data and JSON Validation

Large JSON Validation Errors

A Layered JSON Validation Workflow

A reliable workflow separates parsing from structure and application logic.

Receive or generate the JSON.
Preserve the original input when debugging.
Parse the JSON text.
Fix syntax errors if parsing fails.
Pretty print the successfully parsed data when inspection is useful.
Validate the parsed value against the expected schema.
Inspect the exact failing property path.
Fix missing fields, types, values, or structural issues.
Apply application and business validation.
Send or process the data.
Log safe diagnostic information if the operation fails.
Retest with both valid and invalid examples.

Common Mistakes When Debugging JSON Validation

Several debugging habits make JSON validation failures harder to diagnose.

Calling every JSON error a syntax error.
Changing the schema before checking the input.
Assuming valid JSON means valid API data.
Ignoring the reported property path.
Treating null and missing as identical.
Assuming a number represented as a string is automatically equivalent to a number.
Using JavaScript object syntax as if it were JSON.
Ignoring API status codes.
Formatting sensitive production data through unknown external services.
Silently repairing malformed JSON without reviewing the result.

Calling every JSON error a syntax error.
Changing the schema before checking the input.
Assuming valid JSON means valid API data.
Ignoring the reported property path.
Treating null and missing as identical.
Assuming a number represented as a string is automatically equivalent to a number.
Using JavaScript object syntax as if it were JSON.
Ignoring API status codes.
Formatting sensitive production data through unknown external services.
Silently repairing malformed JSON without reviewing the result.

Best Practices for JSON Validation Errors

Good validation design makes failures easy to diagnose while keeping data and system details protected.

Validate syntax at input boundaries.
Use JSON Schema for reusable structural rules.
Keep business rules separate from basic JSON syntax.
Return field-level errors when practical.
Use stable machine-readable error codes for APIs.
Include precise property paths in validation diagnostics.
Distinguish missing, null, and wrong-type values.
Test boundary conditions and invalid inputs.
Keep schemas and API contracts versioned.
Do not expose secrets in validation messages.
Validate generated and externally supplied JSON before downstream processing.
Document whether unknown properties are accepted or rejected.

Validate syntax at input boundaries.
Use JSON Schema for reusable structural rules.
Keep business rules separate from basic JSON syntax.
Return field-level errors when practical.
Use stable machine-readable error codes for APIs.
Include precise property paths in validation diagnostics.
Distinguish missing, null, and wrong-type values.
Test boundary conditions and invalid inputs.
Keep schemas and API contracts versioned.
Do not expose secrets in validation messages.
Validate generated and externally supplied JSON before downstream processing.
Document whether unknown properties are accepted or rejected.

JSON Formatting Examples

Basic JavaScript JSON Validation

javascript

function parseJSON(text) {
  try {
    return {
      valid: true,
      data: JSON.parse(text)
    };
  } catch (error) {
    return {
      valid: false,
      error: error.message
    };
  }
}

Python JSON Validation

python

import json

def parse_json(text):
    try:
        return json.loads(text)
    except json.JSONDecodeError as error:
        raise ValueError(
            f"Invalid JSON at line {error.lineno}, column {error.colno}: {error.msg}"
        ) from error

Parse Before Schema Validation

javascript

let data;

try {
  data = JSON.parse(jsonText);
} catch (error) {
  throw new Error(`Invalid JSON: ${error.message}`);
}

// Pass `data` to your JSON Schema validator here.

Pretty Print After Successful Parsing

javascript

const data = JSON.parse(jsonText);
const formatted = JSON.stringify(data, null, 2);
console.log(formatted);

Validate JSON from the Command Line

bash

jq . data.json

JSON Validation Error Checklist

Capture the exact JSON that failed.
Determine whether the input is standard JSON or a JSON-like format.
Run a syntax check first.
Read the parser error and location.
Check commas, quotes, colons, braces, and brackets.
Check JSON values and escape sequences.
Confirm that parsing succeeds.
Identify the expected JSON Schema or API contract.
Check required properties.
Check property data types.
Check enum and constant values.
Check arrays and nested objects.
Check string constraints.
Check number ranges.
Distinguish missing properties from null values.
Check unknown or additional properties.
Follow the reported property path.
Check the API status code and response body.
Separate schema errors from business-rule errors.
Retest after the correction.
Test both valid and invalid cases.
Avoid exposing sensitive JSON in logs.
Prefer local validation for sensitive production data.

Frequently Asked Questions

Q:What is a JSON validation error?

It is a failure reported when JSON data does not satisfy the syntax, schema, API contract, or application rules being checked.

Q:Why is my JSON validation failing?

First determine whether the failure is a parsing error, schema error, or application/API error. The fix depends on which layer rejected the data.

Q:What is the difference between a JSON syntax error and a validation error?

A syntax error means the JSON text cannot be parsed. A broader validation error can also mean that valid JSON fails a schema or application rule.

Q:What does unexpected token mean in JSON?

It means the parser encountered a character or token that is not valid at that position. The actual mistake may be immediately before the reported location.

Q:What does unexpected end of JSON input mean?

The JSON ended before the parser found the closing structure or completed value it expected. Missing braces, brackets, or quotation marks are common causes.

Q:How do I fix a JSON validation error?

Identify the failing layer, read the error location or property path, compare the input with the expected syntax or schema, make the appropriate correction, and validate again.

Q:Can valid JSON fail validation?

Yes. Valid JSON can fail JSON Schema validation or an API's contract because required fields, types, values, or structural requirements are not satisfied.

Q:Can valid JSON be rejected by an API?

Yes. APIs can reject syntactically valid JSON because of missing fields, incorrect types, invalid values, authentication, authorization, or business rules.

Q:What causes a missing required property error?

The JSON instance does not contain a property that the schema or API contract requires.

Q:What causes an invalid type error?

The value's JSON type does not match the expected type. For example, a schema may require a number while the input contains a string.

Q:Is a number stored as a string a JSON error?

No. A quoted number such as "30" is valid JSON. It becomes a validation error only when the schema or application expects a numeric value.

Q:What causes an enum validation error?

The value is not one of the values permitted by the schema or API contract.

Q:What causes an array validation error?

The value may not be an array, its items may have incorrect types, its length may violate constraints, or nested items may fail their own validation rules.

Q:What is a JSON Schema validation error?

It means a parsed JSON instance failed one or more constraints defined by a JSON Schema.

Q:Does JSON Schema validate JSON syntax?

Schema validation operates on a JSON instance, so the JSON text normally needs to parse successfully first. Syntax checking and schema validation are separate stages.

Q:Why does the JSON error point to the wrong line?

A parser reports where it detected that parsing could not continue. The actual mistake, such as a missing comma, can occur on the preceding line.

Q:How do I find which JSON field caused validation to fail?

Use the validation error's property path when the validator provides one. Paths such as user.profile.email identify the nested field that violated a rule.

Q:What does a JSON validation path mean?

It identifies the location of the failing value inside the JSON structure, including nested properties and array indexes.

Q:What is the difference between null and a missing JSON property?

A missing property is absent, while null is an explicit JSON value. A schema can treat them differently.

Q:Can optional JSON fields contain null?

Not necessarily. Optional means the property may be absent. Nullable means null is an accepted value. The schema or application must define whether null is allowed.

Q:What causes an additional property validation error?

The JSON object contains a property that the schema or API contract does not permit under its configured rules.

Q:Can comments cause JSON validation errors?

Yes. Standard JSON does not support comments. A strict parser can reject comments even if a JSON-like configuration format accepts them.

Q:Can trailing commas cause JSON validation errors?

Yes. Standard JSON does not allow trailing commas in objects or arrays.

Q:Can single quotes cause JSON validation errors?

Yes. Standard JSON uses double quotes for strings and object property names.

Q:Can formatting fix JSON validation errors?

Formatting improves readability but does not normally repair invalid syntax or make a schema-invalid value conform to the schema.

Q:Should I format JSON before validating it?

You can format successfully parsed JSON to make it easier to inspect. If the input is malformed, fix the parsing problem first.

Q:How do I validate JSON in JavaScript?

Use JSON.parse() to check syntax, then pass the resulting value to a JSON Schema validator when structural validation is required.

Q:How do I validate JSON in Python?

Use json.loads() for JSON text or json.load() for files, then use an appropriate schema-validation library when structural validation is required.

Q:How do I validate JSON from the command line?

Tools such as jq can parse JSON and report syntax errors. Schema validation requires a tool that supports the relevant JSON Schema dialect.

Q:Why does generated JSON pass syntax validation but fail schema validation?

A generator can produce syntactically correct JSON while omitting required properties, using incorrect types, choosing unsupported values, or producing the wrong structure.

Q:Can AI-generated JSON have validation errors?

Yes. AI-generated output can be valid JSON while still violating a required schema or application contract. Treat generated structured data as untrusted until it has been validated.

Q:How do I handle JSON validation errors in an API?

Return structured errors that identify the failing field or constraint when appropriate, use stable error codes, and avoid exposing credentials or internal implementation details.

Q:Should JSON validation happen on the client or server?

Client-side validation can improve user feedback, but server-side validation is still required when the server accepts untrusted input.

Q:Should I validate JSON before sending an API request?

Yes. Check syntax first and validate against the known request contract when practical. The server should still perform its own validation.

Q:Should I validate an API response?

For important integrations, response validation can detect unexpected changes or malformed data before it reaches application logic.

Q:How should I handle validation errors containing sensitive data?

Avoid putting passwords, tokens, personal information, or complete production payloads into error messages and logs unless there is a clear security-controlled reason to do so.

Q:Can a JSON validator repair invalid JSON?

Validation normally reports failures. Repair is a separate operation and any automatic correction should be reviewed before the result is trusted.

Q:What should I do if JSON syntax is valid but validation still fails?

Move to the next layer: compare the parsed JSON with the JSON Schema or API contract, then inspect application-specific rules if the schema passes.