Data Contract Reference
Technical guidance for expected document data, validation, and example payloads.
Data contract reference
Expected data describes the fields a template needs before it can generate a document. The user-facing explanation is in Expected Data.
Contract format
The Suite stores the expected data model as JSON Schema. Use it to describe field names, required values, nested objects, lists, and validation constraints.
Keep field names stable once connected systems depend on them. If a meaning changes, add a new field or create a versioned migration path.
Documentation
Guided tour
Interactive training
Integration guides