Overview
The Schema Validation command provides functionality for:- Validating the current payload against a named tenant JSON Schema (JSON Schema 2020-12)
- Failing the item as invalid when the payload does not match (
incorrect scheme for {name}) - Failing the item as invalid when the schema is missing at runtime (
scheme not found for {name})
Command Type
Command Type ID: 2Parameters
Usage Examples
Validate payload against a named schema
Failure behavior
Check step statistics and the test panel / item error text when invalid counts rise after a transform or schema edit.
Sandbox uses the same validation path. Ensure the named schema already exists for the tenant, then run the step sandbox with a real sample payload.
Common Use Cases
- Contract guard before Sink: Ensure Kafka / RabbitMQ payloads match an agreed ProviderEvent (or other) shape
- Catch transform drift: Fail early when JSONata or mapping output drops required fields
- Tenant-owned contracts: Keep one named schema per output type and reuse it across projects
Related Commands
- Command Validation - String include/exclude checks (VALIDATION id 1)
- JSONata - Shape the payload before schema validation
- Kafka Sink - Publish only after validation passes