Go-live
EDI API go-live checklist
Quick answer
What blocks go-live on our side?
Lab readiness
Prove your customer-side integration: outbound POST validates, the one-shot webhook probe verifies signatures, validation errors are handled, and operators can inspect retained Lab evidence in the dashboard.
- SIGNALEDI_API_KEY in CI secrets
- Webhook handler idempotent on X-SignalEDI-Delivery-ID
- Error alerting on document.delivery_failed.v1 and document.held.v1 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
Use sk_cert_ credentials and Certification-bound partner routes for real partner tests. After partner approval and the Production gate, mint sk_live_ credentials and select the Production binding. The request method and payload stay the same; only the lane identifier and matching credential change.
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
Incomplete mappings, unverified data-flow bindings, missing webhook verification, or absent Production approval block activation. The lane is ready only when Lab evidence and partner Certification are complete.
Partner certification queues, VAN provisioning, and retailer mandate calendars. Track partner status separately from engineering.