EDI Transports

Configure API, SFTP, FTPS, AS2, email, and directory transport while preserving original requests and receipt evidence.

Transport moves a document; it does not establish its business acceptance. Keep original wire, document identity, connection revision, and receipt evidence for each exchange. Transport changes need new testing and current readiness.

Choose a route

Route	Current source surface	Qualification boundary
API/download	Inbound processing and outbound wire responses	Your integration must deliver downloaded outbound bytes
Tenant SFTP client	Encrypted partner/environment connection revisions, polling, upload jobs, history, pause/retire	Pin the host key; test permissions, archive, timeout, and duplicate handling
Tenant FTPS client	Explicit or implicit TLS with protected passive data channels	Verify server certificates and actual partner profile; plaintext FTP is not this route
Hosted SFTP	Tenant mailboxes, key controls, file inspection, retry and purge	Confirm deployed listener, storage, key ownership, and mailbox access
AS2	Signed/encrypted exchange, synchronous/asynchronous MDNs and durable receipts	Qualify certificates, TLS, compression profile, callbacks, and recovery with the actual peer
Email	Managed/BYOS StateSet Mail setup and durable submission receipts	Mail queue acceptance is separate from recipient delivery and EDI acceptance
Directory/VAN	Platform-managed directory pickup/drop and mailbox paths	Requires a real shared persistent mount with multiple replicas

The HTTP inbound API accepts one interchange per request. File workers can split concatenated interchanges; partial batch failure needs inspection of every sibling result. Use the configured source/archive/acknowledgment paths when investigating pickup.

Tenant SFTP and FTPS

Configure a partner’s connection in Connections. SFTP needs host, username, trusted SHA-256 host fingerprint, directories, and password or Ed25519/ECDSA key. RSA-only SSH servers are not supported by the reviewed implementation. FTPS uses verified TLS; qualify explicit/implicit mode and the server’s protected data-channel behavior.

Stored credentials require EDI_CONNECTION_ENCRYPTION_KEY. Pending uploads freeze their original connection, filename, and bytes. Publication uses staging and rename; response loss is reconciled against original bytes. Pausing or retiring a route does not turn its pending work into successful delivery. SFTP and FTPS cannot both be active routes for one partner; test/production mismatches fail closed.

Inspect /v1/connections/sftp/deliveries or /v1/connections/ftps/deliveries, current backoff/holds, and exceptions before resuming work. Independent local fixtures exercise native SSH/FTPS behavior; they do not qualify every partner server.

AS2 receipts

POST /v1/as2 identifies peers through AS2 identity and S/MIME, rather than a bearer key. EDI_AS2_REQUIRE_VERIFIED_INBOUND=true requires verified signed inbound messages. The reviewed provider uses OpenSSL PKCS7/CMS, including supported BER streaming input; it is not the older pure-Rust S/MIME implementation.

Outbound dispatch records tracked work. The worker verifies MDN evidence, retries eligible failures, and retains failed or awaiting-receipt states. For async mode inspect the durable receipt callback at /v1/as2/receipts; for outbound delivery use /v1/deliveries/{id}/evidence. Match message identity, MIC, receipt authentication and processing disposition for the actual attempt. A successful HTTP exchange can carry a negative MDN; missing fields cannot establish acceptance.

The retained OpenAS2 4.14.0 fixture qualifies bidirectional signed/encrypted synchronous exchange and tested compression profiles. Real partner TLS, asynchronous callbacks, certificate rotation, and operational recovery still require their own evidence.

Durable email

Configure managed or bring-your-own StateSet Mail in Connections. Sender verification, explicit permissions, resumable setup, and connection revisions are separate from a successful document exchange. /v1/deliveries/mail returns the newest 200 workspace submissions, attempts, document links, and durable provider receipts.

accepted means Mail queue acceptance; inspect later receipt status. held requires reconciliation; legacy_accepted has no durable provider receipt. Original requests and stable retry keys survive process replacement. Secure signed/encrypted AS1 is outside the reviewed supported scope; ordinary MIME email is not equivalent to AS2.

Platform directory settings

Variable	Default / meaning
EDI_INBOUND_DIR, EDI_OUTBOUND_DIR, EDI_VAN_ROOT	Optional platform-managed paths
EDI_FILE_TRANSPORT_SHARED	Must be true with PostgreSQL and file/VAN paths, attesting shared persistent storage
EDI_POLL_SECONDS	10-second directory poll
EDI_SETTLE_SECONDS	2-second minimum file age
EDI_SFTP_*	Legacy platform SFTP connector; distinct from tenant connection records

A database spool cannot make pod-local emptyDir durable. The legacy environment connector uses its configured platform context; use tenant-bound connections for customer isolation. See configuration and operations.