ModernEDI

Docs

Start with the workflow, then use the references

ModernEDI keeps X12 at the trading-partner boundary while giving your team purpose-built tools to map in both directions: inbound partner X12 into the JSON, XML, HTML, or text your systems use, and outbound source documents back into partner-ready X12 for replies and sends.

Integration API Reference Try Mapper Demo

Getting Started

From blank workspace to visible EDI traffic

ModernEDI does not make X12 your system of record.

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 sends that XML, JSON, or text source document to the /reply API. ModernEDI applies the matching outgoing map to generate and validate the partner's expected X12, then handles the AS2 delivery, receipts, acknowledgments, and transaction linkage around it. The /send API is available for standalone outbound documents. The main ModernEDI workflow keeps X12 at the trading-partner boundary: receive and acknowledge partner traffic, map it into the business document you operate from, then map replies or standalone source documents back into partner-ready X12 when you need to send.

  1. Confirm your workspace endpoint and keys. Check the managed AS2 URL, certificates, and Integration API keys before sharing anything with a partner.
  2. 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.
  3. 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.
  4. Build and publish your first live maps. Use incoming maps to turn representative partner X12 into the operational document format your systems own after receipt, and outgoing XSLT or JSLT maps to turn XML, JSON, or text source documents back into partner-ready X12.
  5. Reply from your system of record. Send your ERP or integration document to ModernEDI, include runtime params when the outgoing map needs values such as BOL numbers, pallet lists, or control numbers, call /reply, and verify the original document, generated reply or send, MDN, 997, payload, and mapped output stay connected in Activity.