Schema checks before integration tests
Partner APIs ship PDFs and sample JSON that drift from published schemas. Running a quick validate here catches null vs missing field debates before you open a vendor ticket.
Required field failures
Missing required keys are listed explicitly—faster than reading a generic 400 from a gateway. Align error messages with what your SDK consumers will see in production.
Complement full CI validation
Use this for ad-hoc payloads. Commit schemas to repo and run ajv or similar in CI for exhaustive keyword support and regression coverage on every pull request.