6.1 Saving Event Feedback using SaveFeedback API

The REST API is used to execute the iHUB Request. API to gather feedback on events that have undergone investigation via an external Case Management system.

End Point Details

This REST API is used for saving feedback.

• HTTP Link - http://<hostname>:<port>//event/event/saveFeedback
• Method – POST
• Content-Type - Application/JSON

Executing SaveFeedback API

To execute the SaveFeedback API, follow the steps mentioned in Executing iHUB Case Status Feedback Request section.

Request JSON Parameters

This section provides the list of parameters for request JSON.

Table 6-1 Parameters and their values

Parameter	Value Type	Description
MIS Date	Date	This date field must be in MM-dd-yyyy format. If the format is incorrect, the request will be rejected.
Event Code	String	Unique Event code on which the event gets generated. Max Length: 30
External Event ID	String	Unique Event ID generated in the external system. Max Length: 50
External Case ID	String	External case ID generated in the external system. Max Length: 50
Event Start Date	Date	This date field must be in MM-dd-yyyy format. If the format is incorrect, the request will be rejected.
Event End Date	Date	This date field must be in MM-dd-yyyy format. If the format is incorrect, the request will be rejected.
Event Decision	String	Decision about the event. Max Length: 4000
Event Priority	String	Priority of the event. Max Length: 50
Event Risk	String	Risk score of the event. Max Length: 50
Event Case Count	String	Case count created as part of the event. Max Length: 5
Event Type	String	Type of the event. Max Length: 30
Data Origin	String	Data origin. Max Length: 20

Response JSON Parameters

There will be no parameters displayed as part of the response.

Request and Response JSON Sample

This section contains request JSON samples for the SaveFeedback API. The entries in this sample are only for reference purposes. Note that if the event code is not present in our system the request will be ignored and the missed out events will be notified in the response.*

Request JSON Sample: 1

[ {

    "misdate": "09-26-2023",

    "eventCode": "4505",

    "extEventID": "1",

    "extCaseID": "1",

    "eventStartDate": "09-26-2023",

    "eventEndDate": "09-26-2023",

    "eventDecision": "CLS",

    "eventPriority": "HIGH",

    "eventRisk": "0",

    "eventCaseCount": 85,

    "dataOrigin": "CMCSMAN",

    "eventType": "AML"

  } ]

Response Sample: 1

Total Number of records in the request:" + 1 + "Number of records Processed:"+ 1

Request JSON Sample: 2

[

  {

    "misdate": "09-26-2023",

    "eventCode": "4505",

    "extEventID": "1",

    "extCaseID": "1",

    "eventStartDate": "09-26-2023",

    "eventEndDate": "09-26-2023",

    "eventDecision": "CLS",

    "eventPriority": "HIGH",

    "eventRisk": "0",

    "eventCaseCount": 85,

    "dataOrigin": "CMCSMAN",

    "eventType": "AML"

  },

  {

    "misdate": "09-26-2023",

    "eventCode": "6262",

    "extEventID": "2",

    "extCaseID": "2",

    "eventStartDate": "09-26-2023",

    "eventEndDate": "09-26-2023",

    "eventDecision": "CLS",

    "eventPriority": "HIGH",

    "eventRisk": "0",

    "eventCaseCount": 85,

    "dataOrigin": "CMCSMAN",

    "eventType": "AML"

  } ]

Response Sample: 2

Total Number of records in the request:" + 2 + "Number of records Processed:"+ 1. The following Event ID(s) are not processed because the associated Event ID(s) are not available in the system.: 6262