About
Using Mir3's SOAP API, an API call is made using a notification id to retrieve a single notification report that matches the inputted id. The SOAP request body is then created with the authentication values and the notification id and passed to the getNotificationReportsOp SOAP Action. If successful, the XML results will contain simple string representations of the fields that the Mir3 API returns. The only exception to this is the Response Options JSON field, which is a JSON representation of the XML that is returned with the User response statistics for the returned notification. This handler is currently using version 4.14 of the Mir3 API.
Configurations
| Name | Description | Sample |
|---|---|---|
| username | Mir3 username. | |
| password | Mir3 password. | ********* |
| enable_debug_logging | Enable debug logging if the value is set to 'Yes'. | No |
Parameters
| Name | Description | Sample |
|---|---|---|
| Notification UUID | The UUID of the notification to retrieve the report for. |
Results
| Name | Description |
|---|---|
| Id | |
| Title | |
| Message | |
| Type | |
| Time Sent | |
| Time Closed | |
| Priority | |
| Status | |
| Contact Attempts | |
| Leave Message | |
| Paused | |
| Closed Cause | |
| Initiator Name | |
| Initiator User Id | |
| Initiator Username | |
| Total Response Count | |
| Total Recipient Count | |
| Total Contacted Count | |
| Total Devices Contacted | |
| Total Phone Seconds | |
| Response Options JSON |
Changelog
Mir3 Notification Report Retrieve V1 (2018-02-08)
- Initial version. See README for details.
Download
GitHub
On This Page
Looking for a workflow engine?
Learn more about the Kinetic Data Enterprise Workflow Platform.
Check it out
Return to Top