.env.example and deployment secret references for the full environment
contract. The settings below cover common operating decisions. The integration variable
EDI_API_TOKEN in client examples contains a scoped key; the same-named server setting
is the platform administrator token.
Core and storage
Event destinations
Customer Sync bindings in Connections carry tenant/environment-specific revisions.
A configured sink or successful setup probe does not establish ERP acceptance. Verify
signed delivery, duplicate handling, and actual downstream objects.
Event delivery signing
These are three different protocols. Verify exact bytes and the relevant timestamp policy.
Timestamped receivers must enforce a bounded time window, verify before parsing, and
persist stable event identity for duplicate handling. Do not substitute one signature
scheme for another. The callback SDK helper
verifies the customer-callback scheme; it is not a Sync-signature verifier.
Transports and cryptography
See transports for supported profiles and receipt boundaries.
Never treat an allowlisted private host as proof of partner ownership or network isolation.
Monitoring and retention
EDI_LOG_FORMAT=json enables structured logs. RUST_LOG controls levels;
OTEL_EXPORTER_OTLP_ENDPOINT enables OTLP traces. Protect telemetry containing identifiers.
Alert channels use EDI_ALERT_WEBHOOK_URL, optional EDI_ALERT_WEBHOOK_SECRET, and
EDI_ALERT_EMAIL_TO with the Mail connector. EDI_ALERT_THROTTLE_SECONDS defaults to 300,
EDI_ACK_SLA_HOURS to 24, and EDI_CERT_EXPIRY_WARN_DAYS to 21.
Current retention defaults are 400 days for documents, usage, dedup, and settled
acknowledgments; 180 for terminal deliveries; 90 for eligible dead letters.
Each has a corresponding EDI_*_RETENTION_DAYS setting; 0 disables that sweep.
See retention details before choosing a replay
window or offboarding policy. Review deployment qualification
for migrations, compatible rollback, and backup evidence.