Traditional EDI uses file-based communication (via VANs, AS2, SFTP, etc.), while API-based EDI uses web services to send/receive data instantly between systems like SAP, Oracle, or Amazon Vendor Central.
1. REST API in EDI
REST APIs are the modern choice for cloud-based EDI platforms (like Cleo, SPS Commerce, or TrueCommerce).
Example: Sending an EDI 856 (ASN) through REST API
Scenario:
Supplier ships goods to Amazon and sends the ASN using an EDI REST API.
Request:
Payload (JSON):
Response:
Advantages of REST EDI:
-
Real-time integration (no waiting for batch jobs).
-
JSON format — easy for modern applications.
-
Better visibility and faster error handling.
2. SOAP API in EDI
SOAP APIs are often used in large enterprise systems (like SAP, Oracle EBS, or healthcare systems) where reliability, security, and transaction validation are critical.
Example: Sending an EDI 850 (Purchase Order) through SOAP API
Request (XML):
Response (XML):
Advantages of SOAP EDI:
-
Strong error handling (ACK/NACK within the response).
-
Secure (WS-Security, encryption, and digital signatures).
-
Reliable delivery (guaranteed message acknowledgment).
No comments:
Post a Comment