Go-live
EDI API go-live checklist
Quick answer
What blocks go-live on our side?
Sandbox readiness
Prove your integration: outbound POST succeeds, webhooks verify signatures, validation errors are handled, and operators see lifecycle in the dashboard.
- SIGNALEDI_API_KEY in CI secrets
- Webhook handler idempotent on X-SignalEDI-Delivery-ID
- Error alerting on document.error events
Partner profile and test transactions
Each trading partner needs an isolated profile. Send required test documents (often 850, 856, 810) and capture ack webhooks as evidence.
Certification and production keys
After partner approval, mint production API keys, update webhook URLs, and switch partnerId references from sandbox to production profiles.
Two-phase truth
SignalEDI can have your API path partner-ready in days, not weeks. Partner mailbox approval is partner-controlled and frequently takes weeks.
FAQ
Common questions
Usually incomplete mappings, missing webhook verification, or undeployed secrets. The API is ready once test traffic flows with green acks.
Partner certification queues, VAN provisioning, and retailer mandate calendars. Track partner status separately from engineering.