You can retrieve (GET) the list of reviewer groups for the specified incident nature.
GET request URL
https://<epo_server_name:port>/rest/dlp/incidents/revgroups/list?incidentNature={n}
Where
epo_server_name:portis 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, reviewer groups set for different data vectors are retrieved.
Request Parameters
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:
| Required | Number |
Using these sample API calls, you can retrieve the list of reviewer groups that are set for incidents generated for data-in-use/motion.
Sample GET request URL
https://172.27.108.53:8443/rest/dlp/incidents/revgroups/list?incidentNature=1
Sample cURL command
curl -k -v -X GET 'https://ePO-url:ePO-port/rest/dlp/incidents/revgroups/list?incidentNature=1' -u '<user>:<password>'
Response parameters
The response to this API call returns the list of assigned reviewer groups for the specified incident nature.
Element | Description | Data type | |
|---|---|---|---|
revgroups | List of reviewer groups for the specified incident nature. The default reviewer groups available in User Management → Permission Sets are:
You can create more reviewer groups as needed and assign users. | string | |
Sample response
{
"1": "Global Reviewer",
"2": "Group Admin",
"3": "Group Reviewer",
"4": "Executive Reviewer"
}Status and error codes
List of HTTP status codes returned for the query.
Code | Description |
|---|---|
200 OK | The response returns the list of reviewer groups. |
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 |