JSON Schema Validator is a comprehensive tool for validating JSON data against JSON Schema definitions. It provides detailed error reporting with field-level validation results.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// JSON Schema Validator response payload
}
}
About the JSON Schema Validator API
JSON Schema Validator works by comparing JSON data against a JSON Schema definition. It validates types, required fields, string patterns, numeric ranges, array constraints, and format specifications.
What people use it for
- API Validation
- Validate incoming API request payloads against defined schemas before processing to ensure data quality
- Configuration Files
- Verify configuration files match expected schemas before deployment to prevent runtime errors
- Data Quality
- Validate data integrity in ETL pipelines by checking against schemas during data transformation
- Contract Testing
- Ensure API responses match contract specifications by validating against JSON schemas in tests
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use JSON Schema Validator
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the JSON Schema Validator API do?
How do I authenticate JSON Schema Validator API requests?
How much does the JSON Schema Validator API cost?
How fast is the JSON Schema Validator API?
What response formats does the JSON Schema Validator API support?
What HTTP method does the JSON Schema Validator API use?
Request parameters — POST /v1/jsonschemavalidator
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
schemaRequired | object | {"type":"object","properties":{"name":{"type":"string"}},"required":["name"]} | The JSON Schema to validate against |
jsonRequired | object | {"name":"John","age":30} | The JSON data to validate |
curl -X POST "https://api.apiverve.com/v1/jsonschemavalidator" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"schema":{"type":"object","properties":{"name":{"type":"string"},"age":{"type":"integer"}},"required":["name"]},"json":{"name":"John Doe","age":30}}'Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
content-typeRequired | POST body | application/json |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — POST /v1/jsonschemavalidator
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"valid": true,
"errors": [],
"error_count": 0
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
valid | boolean | true | Whether the JSON data is valid against the schema |
errorsPremium | array | [] | Array of validation error messages |
error_count | number | 0 | Number of validation errors found |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | JSON Schema Validator calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — POST /v1/jsonschemavalidator
No SDK to install — this is a plain HTTPS call to /v1/jsonschemavalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/jsonschemavalidator" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — POST /v1/jsonschemavalidator
Install the Node.js SDK, then call the JSON Schema Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/jsonschemavalidatorconst res = await fetch("https://api.apiverve.com/v1/jsonschemavalidator", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — POST /v1/jsonschemavalidator
Install the Python SDK, then call the JSON Schema Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-jsonschemavalidatorimport requests
res = requests.get(
"https://api.apiverve.com/v1/jsonschemavalidator",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — POST /v1/jsonschemavalidator
Install the C# / .NET SDK, then call the JSON Schema Validator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.JSONSchemaValidatorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/jsonschemavalidator");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — POST /v1/jsonschemavalidator
No SDK to install — this is a plain HTTPS call to /v1/jsonschemavalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/jsonschemavalidator", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — POST /v1/jsonschemavalidator
No SDK to install — this is a plain HTTPS call to /v1/jsonschemavalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/jsonschemavalidator");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — POST /v1/jsonschemavalidator
No SDK to install — this is a plain HTTPS call to /v1/jsonschemavalidator with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/jsonschemavalidator")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive JSON Schema Validator form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — JSON Schema Validator API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the JSON Schema Validator API.
Text Processing
- Acronym Expander
- Anagram Detector
- Antonym Finder
- Cron Expression Parser
- Data Masking
- Did You Mean
- Emoji Decorator
- Gibberish Detector
- Grammar Check
- ISBN Validator
- JSON Schema Validator
- Keyword Extractor
- Leet Speak
- Levenshtein Distance
- Line Sorter
- Markdown Link Extractor
- Palindrome Checker
- Parts Of Speech
- Phonetic Encoder
- Pig Latin
- Profanity Filter
- Reading Time Calculator
- Regex Tester
- Remove Punctuation
- Reverse Text
- Rhyming Words
- Slugify
- Spell Checker
- Syllable Counter
- Tax ID Validator
- Tense Converter
- Text Language
- Text Lemmatizer
- Text Readability Score
- Text Similarity
- Text Styler
- Text Summarizer
- Text to Emoji
- Title Case Converter
- Translator
- Vowel Counter
- Website Readability
- Word Lexicon Analyzer
- Word Opposites
- Word Pronunciation
Related articles
All articles →
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read 
Summarize Text with AI: A Practical GuideUse AI to summarize articles, documents, and user content. Tutorial with code for content platforms, research tools, and dashboards.Read 
7 Content Moderation Mistakes That Sink AppsYour app allows user content. Here are the moderation mistakes that get apps pulled from stores.Read