What JSON Schema does
JSON Schema describes constraints on JSON data. A validator checks a document against those constraints and reports whether it conforms. This is different from parsing: a JSON string can be syntactically valid while violating your API's contract.
A minimal useful schema
Start with an object, explicit required properties, and type constraints. For example: {"type":"object","required":["id","amount"],"properties":{"id":{"type":"string"},"amount":{"type":"number","minimum":0}}}. A missing amount fails even if the JSON parses successfully.
Required does not mean nonempty
The required keyword checks property presence, not whether a string contains meaningful text. Combine it with minLength where needed. Similarly, type: "number" allows decimals; use integer when fractions are invalid.
Use formats carefully
A format such as date-time can describe the intended representation, but whether it is enforced depends on the validator's configuration and supported draft. Do not assume that every validator treats format as a hard assertion.
Handle evolving payloads
Be careful with additionalProperties: false on third-party APIs. It can reject otherwise compatible provider additions. Consider explicitly allowing unknown properties while strictly validating the fields your consumer depends on. Version schemas when breaking changes are intentional.
Put validation in the request path
Validate before persisting or acting on data, return stable error categories, and avoid echoing secrets in error reports. Zorqelio supports deterministic JSON contract validation; start with the public playground or quickstart.
For implementation details and current capabilities, consult the Zorqelio documentation. Technical examples are illustrative and should be tested against your own policies and supported schema dialect.