Skip to main content
The Schema Validation command (Command Type: 2) checks that the previous command’s payload matches a named JSON Schema stored for your tenant. On success the payload is unchanged and the Blueprint continues. On failure the command throws, the step run counts as invalid, and no results from that run reach child steps or sinks.

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: 2

Parameters

Usage Examples

Validate payload against a named schema

Place Schema Validation after parse/transform commands and before a Sink so only contract-compliant payloads are published.

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