Mappings and payloads
Define mappings and payload contracts for every EDI lane
Quick answer
Why can a type support raw send but not typed send?
Four payload representations
Raw is the exact admitted wire document. Structured is core parser output. Document is a tested registry projection available only when typedReceive=true. Mapped is the durable output of the account's approved mapping; canonical remains a compatibility alias for mapped.
Mapping specification
For every type and direction, define source and target paths, cardinality, data types and precision, qualifiers, code lists, date and time rules, required conditions, safe defaults, reject or hold behavior, implementation-guide evidence, and data classification. Defaults cannot invent partner, routing, payment, or clinical facts.
Deterministic Lab and partner certification
In Lab, test missing and maximum values, duplicate business and idempotency keys, multiple and mixed messages, code-list errors, delimiter data, envelope counts, declared-type mismatch, lossless encodings, and mapping output for both EDI and API inputs. In Certification, add ambiguous partner identities, authority changes before egress, real endpoint outages, and accepted, rejected, late, duplicate, or missing acknowledgements.
Schemas and executable examples
GET /v1/document-types/{code}/schema returns the current typed-send schema when one exists. Raw input uses content or contentBase64 plus contentEncoding. The generated payload and message catalog is derived from the same executable registry used by validation and the TypeScript SDK.
- Schema version: 2026-09
- Exactly one of payload, content, or contentBase64
- Raw standard and document type assertions must match the bytes
FAQ
Common questions
Raw support means the platform can preserve, inspect, authorize, and route the message. Typed support additionally requires a stable public business schema, validator, canonical projection, and tested renderer.
Every contained type must have authority. A typed receive projection is returned only when the requested transaction is unambiguous; repeated same-type messages return an explicit unavailable result instead of selecting one.