Incident APIs

Companies that own or link to Agile Process Teams use these APIs to add, update, and resolve general supply chain incidents on the Owner's network. Partners must be a member of the Owner company's network to collaborate with the Owner on an incident. For example, a Manufacturer's internal location might have a material shortage that impacts production and needs to be investigated by the Supplier, or a 3PL might need to report to the Manufacturer that shipping labels are missing. After adding the incident, both parties can collaborate to investigate and resolve the reported problem. Partners must be a member of the Owner company's network to collaborate with the Owner on an incident.

Incidents can be in one of three base workflow states:

  • To Do – The incident is new and has not been reviewed. This state is applied to new incidents that are not submitted to Partner or created by a Partner user. Can be transitioned to Under Investigation or Closed.
  • Under Investigation – The incident has been reviewed and is ready for investigation by assigned users. This state can be manually applied. It is automatically applied when an incident is submitted to Partner and when a closed incident is reopened. Can be transitioned to Closed by closing the incident.
  • Closed – The incident is resolved. This state is automatically applied when the resolution is submitted. Can be transitioned back to Under Investigation by reopening the closed incident.

Add Incident

Owners and Partners use this API to add a new general incident to the Owner company's network, including any initial comments or file attachments. The response returns a generated identifier for the new incident. Notification timers are created based on the entered due dates for alerts.

New incidents are assigned the ToDo base state by default.

Edit Incident

Owners and Partners use this API to to do the following: 

  • Modify an existing general incident with new, updated, or corrected information and documentation (e.g. adding an initial response, fixing a typo, updating the root cause notes for a closed incident).
  • Update the incident workflow state (e.g. manually transitioning the base state from To Do to Under Investigation to indicate that the incident has been reviewed and submitted for investigation).
Use the shared comment APIs to add, edit, or delete comments and file attachments. These APIs are shared across all incident types.

Copy Incident

Owners and Partners use this API to copy an existing incident to the network. A boolean field determines whether to the linked processes from the original to the new incident.

The new incident is assigned the To Do base state.

Close Incident

Owners and Partners use this API to close an existing general incident. A closing statement and resolution type must be provided.

The closed incident transitions from its current base state (either To Do or Under Investigation) to a Closed state. Closed incidents can be edited or reopened by users with the requisite permissions.

Reopen Incident

Owners use this API to reopen a closed general incident. The response returns the identifier of the reopened incident. The system reopens the incident with all information intact, except the base state is updated from from Closed to UnderInvestigation. Reopened incidents cannot be transitioned back to the initial ToDo base state.

Submit Incident to Partner

Owners use API to submit an existing general incident to the Partner specified in the incident partnerId. This cannot be undone.

Upon successful response:

  • isSubmittedToPartner updates to true.
  • The incident becomes visible to the Partner.
This API does not update the incident's base workflow state. Use the Edit API to transition the incident from one workflow state to another.