Validate JSON payload

Use this page when the API returns a 400 or validation error for a create/update request and the problem is hard to spot by eye. Paste the JSON payload you are about to send for an event, location, venue, or route.

What this validates

The validator checks a full TRCItem draft against TRCItemSchema from @eventconnectors/ndtrc_model. It catches schema and field-format problems such as:

• invalid URLs, for example contactinfo.urls[1].url: ".."
• invalid enum values such as an unknown wfstatus, entitytype, filetype, or urlServiceType
• invalid language codes such as nl-NL where the model expects a two-letter lowercase code like nl
• invalid time strings such as 25:00
• values with the wrong JSON type, for example a string where a boolean is expected

A successful result means the payload matches the published TRCItem draft schema. It does not guarantee the API will accept and store the item: server-side business rules, account permissions, linked resources, editorial workflow, and duplicate handling can still reject or change a request.

Validation modes

• API-compatible mode uses the same permissive behavior as the TypeScript schema package. Unknown fields are allowed, which matches how the API can tolerate or return fields that older clients do not yet understand.
• Strict mode rejects unknown fields anywhere in the payload. Use it to find likely typos in JSON you control, but remember that strict-mode failures are not always API failures.

Full payloads only

This tool validates a complete TRCItem draft. It does not validate isolated sub-objects such as only calendar, contactinfo, or files.

If you want to validate sub-objects in your own code, import the relevant schema from @eventconnectors/ndtrc_model, for example CalendarSchema, ContactinfoSchema, or FileSchema.