Message Disposition Notification (MDN) tracking in the Celigo platform (integrator.io) provides an automated, audit-ready governance framework to verify B2B EDI message delivery over AS2 connections. The platform persistently saves, encrypts, and indexes inbound and outbound MDN acknowledgments for every transaction without requiring you to turn on connection debugging. This operational visibility ensures you can satisfy strict trading partner agreements, fulfill corporate compliance requirements, and resolve supply chain disputes.
Before tracking AS2 MDN records, ensure you meet the following requirements:
-
Subscription plan: You must have a B2B Manager subscription to access persistent MDN storage and the EDI activity dashboard.
-
Account permissions: You must have integration-level view or manage permissions to access MDN payload details and signature verification data.
-
API access: Admin credentials and explicit role-based API access are required to query MDN records programmatically via the platform developer endpoint.
The platform automatically logs receipt verification status tokens and signature payloads across both synchronous and asynchronous AS2 message exchanges.
During synchronous processing, the MDN receipt generates and transfers in real time within the active HTTP/S connection session.
|
Direction |
Operational lifecycle |
|---|---|
|
MDN for outbound EDI |
You send an EDI document to a trading partner. The partner system processes the incoming payload and immediately returns a signed MDN receipt over the open request connection. |
|
MDN for inbound EDI |
A trading partner sends an EDI file to your integrator.io listener step. The platform validates the payload signature and generates a signed MDN response back to the partner before closing the session. |
During asynchronous processing, your trading partner decouples message receipt from processing. Transmission details pass over separate, isolated HTTP/S transaction loops.
|
Direction |
Operational lifecycle |
|---|---|
|
MDN for outbound EDI |
You send an EDI file to a trading partner. The partner acknowledges receipt, closes the initial connection session, and delivers the finalized MDN receipt over a separate inbound session. If the incoming asynchronous MDN encounters connectivity issues, it is subject to standard platform timeout limits. |
|
MDN for inbound EDI |
A trading partner sends an EDI file into your flow. The platform parses the payload and sends a response confirming receipt. After downstream processing finishes, integrator.io opens a separate connection to send the signed MDN to your partner. |
You can verify and extract compliance records from the EDI dashboard or using API calls.
Go to Dashboard > EDI Activity to view the status, transmission timestamps, and verification data for your transactions. Check the Actions column for the MDN activity log.This interface displays the processing metrics you need to troubleshoot unacknowledged transmissions or missing transactions without inspecting raw flow error queues. The MDN logs persist and you can check them, if required, for any specific period.
Query platform endpoints programmatically to download acknowledgments. Every programmatic retrieval event is cataloged inside your account audit logs to ensure compliance and traceability.
You can download an acknowledgment using the following API call:
POST /v1/ediTransactions/{_transactionId}/mdn
To get the transaction ID, use the following API call
POST (v1/ediTransactions/query
For more information, see the Celigo developer docs.