Getting Started
From blank workspace to visible EDI traffic
Inbound X12 is mapped into the ERP, WMS, accounting, XML, JSON, or custom document shape your operation actually uses. That mapped document should become the source of truth for review, changes, fulfillment, and billing.
When you need to send a reply such as an ASN or invoice, your integration transforms
that source document into the partner's expected X12 and calls the
/reply
API. ModernEDI handles the AS2 delivery, receipts, acknowledgments, and transaction
linkage around it. The
/send
API is available for standalone outbound documents, but the main ModernEDI workflow
starts with partner traffic and moves your team out of X12 into the business document
you actually operate from.
- Confirm your workspace endpoint and keys. Check the managed AS2 URL, certificates, and Integration API keys before sharing anything with a partner.
- Run the ModernEDI test partner. Receive a test 850 order, reply with an 810 invoice, and confirm the MDN, 997, mapped output, stored payload, and reply link are connected.
- Add your first real AS2 connection and partner profile. Enter partner identifiers, URLs, certificates, signing and encryption choices, then use the setup sheet to hand off your ModernEDI values.
- Build and publish your first live map. Use the mapper to turn representative inbound X12 into the operational document format your systems will own after receipt.
-
Reply from your system of record.
Generate partner-ready reply X12 from your ERP or integration document, call
/reply, and verify the 850, 810 or 856, MDN, 997, payload, and mapped output stay connected in Activity.