edi connectors¶
Electronic Data Interchange integrations. These cover secure transport + healthcare/retail-specific protocols. As of 2026-05-22 the former naive x12 and edifact connectors were removed in favour of the first-class edi:// component (backed by omniparser) — schema-driven, streaming, with proper segment-group / loop support. Use the edi:// component for X12 / EDIFACT parse / generate; the connectors below cover everything else.
Connectors in this category¶
| Connector | URI / type | Auth | Native SDK | One-line description |
|---|---|---|---|---|
as2 |
connector://as2/send |
Certificate (MIC + signing) | No (HTTP) | AS2 (RFC 4130) secure EDI messaging over HTTP with MDN receipts. |
fhir |
connector://fhir/send |
OAuth2 / Bearer | No (HTTP) | HL7 FHIR R4 / R5 RESTful healthcare resource CRUD. |
hl7 |
connector://hl7/send |
MLLP / TLS | No (HTTP) | HL7 v2.x pipe-delimited message send / parse over MLLP. |
rosettanet |
connector://rosettanet/send |
mTLS / signing | No (HTTP) | RosettaNet Partner Interface Processes (B2B supply-chain). |
tradacoms |
connector://tradacoms/send |
None | No (HTTP) | TRADACOMS UK retail EDI parse / generate. |
X12 + EDIFACT moved to the
edi://component — seepkg/component/edi/and the edi component reference. Schema-driven via omniparser; supports streaming and loop / segment-group correctness that the old connector lacked.
See also¶
- Connector SDK guide — adding a new connector
edi://component reference — primary X12 / EDIFACT integration path- enterprise — DocuSign for e-signature B2B flows