Upload schemas and request/response payloads to run schema-aware validation. XML and JSON are supported — no code required.
1Choose validation type
2Select or upload schema(s)
Choose schemas from your library or upload new ones. Uploaded schemas are saved for future runs.
Schema library
Upload additional schema files — they are checked for syntax and structure, then stored automatically.
Drop schema file(s) here or click to browse
.json
Up to 50 MB per file
3Canonical mapping
Canonical mapping applies only when using the JSON Schema validator. Select JSON Schema in step 1 to configure mapping and XML transform options.
3Canonical mapping
A canonical mapping workbook is generated automatically from your uploaded schema(s).
Optional: replace auto-generated mapping
.xlsx
Up to 50 MB per file
3Advanced: canonical XML transform
Optional. Apply a mapping workbook to transform raw XML into the canonical JSON shape before validation.
4Upload samples to validate
Upload request and response files together. XML is beautified first, then classified from request/response tags in the content.
Drop sample files here or click to browse
.xml, .json — request/response auto-detected
Up to 50 MB per file
5Choose what to validate
Pick request samples, response samples, or validate everything.
All samples
Validate every uploaded sample
Request only
Validate inbound/request payloads
Response only
Validate outbound/response payloads
Step 1 of 5
✓Validation results
A record of validation runs from this browser. Open a run to review its results, schema gaps, and converted payloads.
Run detail
Your persistent schema library. Upload schemas here or from the Validate wizard — they are stored on the server and available for every validation run.
Drop schema file(s) here or click to browse
.json — checked and stored in your schema library
Up to 50 MB per file
Compare XML samples against a schema to find missing fields that should be reviewed and optionally added.
1Choose schema
Select a schema, or upload one below to add it to the library and use it here.
Drop schema file here or click to browse
.json
Up to 50 MB per file
2Upload XML samples
Upload one or more XML samples. The tool scans every element and attribute in each file.
Drop XML sample files here or click to browse
.xml — multiple files supported
Up to 50 MB per file
Select a schema and upload XML samples.
✓Missing fields analysis
Scan XML samples for fields under any *Extension container, with full XPath for each field. Download the list as Excel when ready.
1Upload XML samples
No schema required. Upload one or more XML samples to list extension fields. Fields named tc are ignored.
Drop XML sample files here or click to browse
.xml — multiple files supported
Up to 50 MB per file
Upload XML samples to list extension fields.
✓Extension fields found
Generate a canonical mapping Excel document from a JSON schema. ACORD XML paths are resolved from your uploaded XSD set — blank when a field is not present in the XSD.
1Choose schema
Select a stored schema, or upload one below to add it to the library and use it here.
Drop schema file here or click to browse
.json
Up to 50 MB per file
2Upload ACORD XSD
Upload the full ACORD XSD set in one drop. TXLife alone will be rejected because it includes siblings — select all of: TXLife2.15.00.xsd, XMLife2.15.00.xsd, XTbML2.15.00.xsd, XlifeBase2.15.00.xsd, OLifeExtension.xsd, and TypeExtension.xsd.
Drop XSD file(s) here or click to browse
.xsd — upload TXLife and all included siblings together
Select a schema and upload XSD file(s).
3Document format
The Excel file includes these columns, with fields grouped under each object title:
JSON Parent
JSON Object/Attribute
JSON Type
ACORD XML Path (XSLT Path) — from XSD only; blank if not in XSD
Compare an older schema with a newer one by field path and datatype, then upgrade the older schema with selected changes.
1Older schema
Drop older schema or click to browse
.json
2Newer schema
Drop newer schema or click to browse
.json
Select older and newer schemas to compare.
✓Schema differences
Select upgradable rows (added fields / type changes), then upgrade the older schema.