To integrate IUNGO BDI with your ERP, explore the exchange flow, POP, ACK, and PUSH operations, activation phases, and technical documents. The connection between BDI and the supplier's ERP is the responsibility of the supplier.
IUNGO Business Data Integration is the solution that allows to automate the exchange of business documents between customers and the suppliers integrated on the IUNGO platform.
Back to features and benefits
Connection methods and parameters specified for each operational endpoint.
Download a document from IUNGO BDI.
This allows the Partner to download all documents that were forwarded to him, one at a time.
English
Italianohttpsicn.iungoapps.comPOSTv2.0/webapi/pop/orders
v2.0/webapi/pop/ordrsp
v2.0/webapi/pop/desadv
application/xmlBearer APIKEYConfirm the download operation.
This allows the Partner to confirm the correct download of a document from the IUNGO BDI platform.
httpsicn.iungoapps.comPOSTv2.0/webapi/ackreceiptHandleBearer APIKEY{receiptHandle} is automatically generated for each document and is used to confirm the document download
Upload a document to IUNGO BDI.
This allows a Partner to connect and send a document to IUNGO BDI.
httpsicn.iungoapps.comPOSTv2.0/webapi/push/orders
v2.0/webapi/push/ordrsp
v2.0/webapi/push/desadv
application/xmlBearer APIKEYActivation must be carried out independently by the user.
The RUNBOOK describes all the use case tests required for full integration.
A "TEST Business Partner" named "IUNGObptest" is available on the platform to test and validate the BDI service integration using certified use cases. This is a fictitious company designed for testing purposes.
Test document download and upload of data acquisition confirmation.
Test updating order lines across all order types, verifying split management where applicable.
Test sending of DESADV (Advance Shipping Notice).
Direct links to integration specifications, schema definitions, and testing files.
Document detailing technical connection to the platform.
Open documentXML specification document used to communicate with the platform.
Open documentSchema detailing the technical structure of ORDERS and ORDRSP.
Open schemaSchema detailing the technical structure of DESADV.
Open schemaTemplate detailing test execution and validation steps.
Open fileSample XML payloads for technical reference and mapping.
Open archiveNO, it is up to the sender to decide which and how many documents to send (or not to send) to the recipient. Therefore, it is the supplier's responsibility to decide whether to send all confirmations and/or Desadv to the customer, just as it is the customer's responsibility to decide whether to send all orders to the supplier and update them after each change.
YES, the IUNGO BDI service only verifies compliance with the format for each document type and the presence of "mandatory data" (as indicated in technical specifications). The business content of exchanged data falls entirely within the autonomy and responsibility of the sender.
BDI ensures document delivery and payload syntax validation, but not semantic business meaning. The semantic meaning of data contained in exchanged documents and custom business rules must be agreed between partners outside of the platform.
NO, IUNGO BDI guarantees the presence of "mandatory" data required by the communication standard. If a document does not contain mandatory information, IUNGO BDI rejects it, notifying the sender. It is the sender's responsibility to populate the "optional" fields needed by the recipient.
IUNGO does not build the connection between BDI and the supplier's ERP. Connecting to BDI is the responsibility of the supplier.