⚙️ Introduction

This job exports Order Incidents from DJUST to an external system via the API Connector.

You can:

• Export an Incident declared on an Order or on one or several Order Lines
• Export the reason of the Incident and the affected Order Lines with their quantities
• Map each DJUST field to the body parameter expected by your API

📂 Export model

API Connector

The API Connector pushes one JSON payload per Incident to your endpoint. The content of the payload is defined by the mapping configured on the job: each DJUST field is mapped to the body parameter expected by your API.

{
 "orderIncidentId":"INCIDENT_1234",
 "orderIncidentExternalId":"4567",
 "orderReference":"172-189-1896838-1",
 "createdAt":"2024-06-04T10:30:00Z",
 "incidentStatus":"OPEN",
 "reasonCode":"RC001",
 "reasonDescription":"Broken product on delivery",
 "supplierExternalId":"SUPP_321",
 "accountExternalId":"ACC_777",
 "orderLineIncident":[
    {
       "orderLineId":"16841984844",
       "orderLineExternalId":"OLINE_5678",
       "incidentLineStatus":"OPEN",
       "variantExternalId":"489156",
       "incidentLineQuantity":1
    }
 ]
}

📋 Fields

The fields below are the DJUST fields available in the mapping panel of an API Connector export job. The keys shown in the example above are the DJUST default names — map each of them to the name expected by your API.

Incident level

Order Line Incident level

🧠 Key Business Rules

• An Incident is exported only once per status. Reaching the same status again does not trigger a new export.
• The Incident status and the statuses of its lines are independent: closing an Incident does not close its lines, and closing every line does not close the Incident.
• An Incident declared at Order level has no orderLineIncident entries; an Incident declared at Order Line level carries one entry per impacted line.
• Custom Fields are not exported on Incidents, even when they are declared on the Incident or on its lines.
• Only one endpoint per export job is supported.
• Incident statuses can be fed back into DJUST by your ERP, either through a Data Hub import or through the administration API — see Updating incident statuses.