REST API call to retrieve the list of users assigned as reviewers

You can retrieve the list of users assigned as reviewers to incidents of a specific incident nature.

https://<epo_server_name:port>/rest/dlp/incidents/revusers/list?incidentNature={n}

Where

epo_server_name:port is the server IP address and port number.
incidentNature={n} n can be 1, 2, or 3 for incidents of different data vectors (incident nature). Based on the value of n specified, the users assigned as reviewer are retrieved.

Parameter name	Description	Required	Values
Authorization	User credentials for ePO - On-prem.	Required
incidentNature={n}	Incidents generated for data-in-use/motion and data-at-rest can have the same incident IDs. Specify n to differentiate the incident nature. Based on the data vectors, {n} can be: 1 = Incidents generated for data-in-use/motion 2 = Reserved for data-at-rest - Endpoint Discovery incidents and can be used when support for Endpoint Discovery custom attributes is added into the product 3 = Incidents generated for data-at-rest - Network	Required	Number

In these sample requests, list of users assigned as reviewers for incidents generated for data-in-use/motion is retrieved.

Sample GET request URL

https://172.27.108.53:8443/rest/dlp/incidents/revusers/list?incidentNature=1

Sample cURL command

curl -k -v -X GET 'https://ePO-url:ePO-port/rest/dlp/incidents/revusers/list?incidentNature=1' -u '<user>:<password>'

The response to this API call returns a list the users assigned as reviewers for users based on the specified incident nature.

Element		Description	Data type
revusers		Users assigned as reviewer for the specified incident nature.	string

{
    "8": "user1",
    "9": "user2"
}

List of HTTP status codes returned for the query.

Code	Description
200 OK	The response returns a list of users assigned as reviewer.
400 Bad Request	incidentNature is missing or has a non-numeric value.
404 Not Found	Incorrect ePO - On-prem URL.
500 Internal Server Error	An error on the server side that failed the request. See the ePO - On-prem `orion.log` file for more details about the error.