Cluster C1: JSON Ecosystem
JSON schema validation checklist
Contract drift between producers and consumers is one of the most common sources of API regressions. A schema checklist in CI and runtime guards keeps payload expectations explicit and prevents silent type mismatches.
Checklist for production teams
- Version schemas and keep backward compatibility notes with each change.
- Validate request and response payloads in CI for representative fixtures.
- Reject unknown critical fields when strict mode is required.
- Track validation failure rates by endpoint to detect contract drift early.
Practical input/output example
Input schema rule
"properties": {
"amount": { "type": "number" }
}Output validation
payload: {"amount":"100"}
result: invalid (string vs number)