Free JSON validator API

Paste JSON and check its syntax. The answer says valid true or false at once, and a small report with the parser message is stored for 24 hours, for invalid JSON too. The form calls the same free API your code can call.

The whole API
curl -s -X POST https://aisenseapi.com/services/v1/json_validate \
  -H "Content-Type: application/json" \
  -d '{"data":"{\"active\":true,}"}'

{
  "storage_id": "ebcabcff-b3e7-46b1-8920-c27671deedb2",
  "storage_url": "https://aisenseapi.com/services/v1/storage/ebcabcff-b3e7-46b1-8920-c27671deedb2",
  "sha256_hash": "936d3fd69bca8892f601b7ab0cce7f3decd1bb11ee8b02a90009a0931b0bff02",
  "bytes": 71,
  "expire_timestamp": 1790760065,
  "expire_datetime": "2026-09-30T09:21:05+00:00",
  "content_type": "application/json",
  "filename": "validation.json",
  "operation": "json_validate",
  "valid": false
}
No API key No account Syntax check Report for every check 5000 req / IP / 24h

Try it in the browser

This form posts to the same endpoint and shows the stored result. What you enter is sent to aisenseapi.com, and the result is kept for 24 hours at a link that anyone with the link can open.

Drop a JSON file here or click to choose one

What is checked

The report stored for the example at the top of the page:

{"valid":false,"error":"Syntax error","input_bytes":16,"max_depth":128}

The API

POST https://aisenseapi.com/services/v1/json_validate with Content-Type: application/json. The JSON to check goes in as text, in a string.

FieldRequiredMeaning
datayesThe JSON text, as a string.

The answer adds valid to the Storage fields, so a client can act without reading the report. The report is stored as validation.json with valid, error, input_bytes and max_depth.

The answer is a Storage link

The endpoint never sends the converted file in its answer. It stores the result for 24 hours and answers with the same fields the Temporary Storage API answers with, plus what the result is:

FieldMeaning
storage_id, storage_urlWhere the result is. A GET on the URL returns the bytes.
sha256_hash, bytesThe digest and size of the stored bytes.
expire_timestamp, expire_datetimeWhen the result is removed, 24 hours after it was stored.
content_type, filenameWhat the result is and the name to save it under.
operationThe endpoint that made it.

The id and the expiry in the examples on this page come from a test run and are different on every call. The hash and the size are what the example request gives every time.

Anyone with the link can read the result until it expires, so do not send personal or confidential data. Stored results count against the Storage budget of 80 MB per IP address per day.

Limits

Errors

A refused request stores nothing and answers with error. The endpoint's own refusals also carry fix, a sentence saying what to send instead.

StatusWhen
400The body is not a JSON object, a field is missing, unknown or has the wrong type, or the input breaks the rules above.
405The method is not POST.
413The request, the rows or the result is over a limit.
415The Content-Type is not application/json.
429More than 5000 requests from one IP address in 24 hours, or the day's Storage budget is used up.
503The result could not be stored. Try again later.

Questions

Is the JSON validator API free?

Yes. No API key, no account and no sign up. The limit is 5000 requests per IP address per 24 hours, and stored reports count against the Storage budget of 80 MB per IP address per day.

Does it check against a JSON Schema?

No. It checks syntax only: whether the text is valid JSON.

Why is a report stored when the JSON is invalid?

Finding invalid JSON is a completed check. The answer says valid false, and the stored report with the parser message can be passed on as a link.

Does it tell me the line of the error?

No. The report carries the parser message, such as Syntax error, without a line or column.

All conversion endpoints All free public APIs