The GET Priority Matrix Incident Master API retrieves Priority Matrix master data from the Incident Management (IM) module. The API response returns the mappings used to derive an Incident Priority from the selected Impact and Urgency values.
The API supports the following operations:
Retrieve List of Priority Matrix Master Records
This endpoint retrieves all Priority Matrix records configured in the Incident Management module. Administrators, integrations, and automation tools can use the endpoint to review Priority calculations, check configuration, synchronize mappings, and support reporting.
Endpoint
GET /API/v1/Master/IM/PriorityMatrixComponent | Value | Description |
|---|---|---|
HTTP Method | GET | Retrieves data from the server. This is a read-only operation, update, or delete records. |
API | API | Stands for Application Programming Interface . It provides a standard way for applications to communicate with the system and exchange data. |
Version | v1 | Indicates Version 1 of the API. Versioning helps maintain compatibility when developers introduce new API versions. |
Resource Group | Master | Refers to the Master Data module, which contains reusable reference data such as Categories, Priorities, Statuses, and Priority Matrix mappings. |
Module | IM | Stands for Incident Management . It identifies that the requested master data belongs to the Incident Management module. |
Resource | PriorityMatrix | Specifies the Priority Matrix master data resource. Each record maps an Impact and Urgency combination to a resulting Priority. |
Request Headers
{
"Accept": "application/json",
"X-Api-Key": "<API_KEY>"
}
Header | Value | Required | Description |
|---|---|---|---|
Accept | application/json | Yes | Requests the API to return the response in JSON format. |
X-Api-Key | <API_KEY> | Yes | API key used to authenticate and approve the caller. |
Sample Request
The following cURL request sends an HTTP GET request to retrieve all Priority Matrix master records. Replace <API_KEY> with a valid API key. Replace {host} with the appropriate server address when calling the API from another environment.
curl --location '{host}/API/v1/Master/IM/PriorityMatrix' \
--request GET \
--header 'Accept: application/json' \
--header 'X-Api-Key: <API_KEY>'
Sample Response
The following sample response returns an array of Priority Matrix records. Each object represents one configured mapping between Impact, Urgency, and Priority. For example, the first record maps High Impact and High Urgency to the Critical Priority. The second record maps Medium Impact and Medium Urgency to the High Priority.
[
{
"UID": 1001,
"Active": true,
"Impact": 1,
"Impact_Text": "High",
"Urgency": 1,
"Urgency_Text": "High",
"Priority": 1,
"Priority_Text": "Critical",
"Priority_Text_Display": "P1 - Critical",
"Instance": "Info",
"Instance_Text": "Info"
},
{
"UID": 1002,
"Active": true,
"Impact": 2,
"Impact_Text": "Medium",
"Urgency": 2,
"Urgency_Text": "Medium",
"Priority": 2,
"Priority_Text": "High",
"Priority_Text_Display": "P2 - High",
"Instance": "Info",
"Instance_Text": "Info"
}
]
::: {custom-style="Callout Blue"}
[Note:]{custom-style="Callout Label"}
The sample values are illustrative. Actual values depend on the Priority Matrix configuration in the tenant
:::
Response Fields
Field | Type | Example Value | Description |
|---|---|---|---|
UID | Integer | 1001 | Unique identifier of the Priority Matrix record. |
Active | Boolean | true | Indicates whether the Priority Matrix record is active and available for use. |
Impact | Integer | 1 | Identifier of the Impact value used in the mapping. |
Impact_Text | String | "High" | Display text of the mapped Impact value. |
Urgency | Integer | 1 | Identifier of the Urgency value used in the mapping. |
Urgency_Text | String | "High" | Display text of the mapped Urgency value. |
Priority | Integer | 1 | Identifier of the Priority produced by the Impact and Urgency combination. |
Priority_Text | String | "Critical" | Text value of the resulting Priority. |
Priority_Text_Display | String | "P1 - Critical" | Formatted display name of the resulting Priority. |
Instance | String or Integer | "Info" | Identifier or value of the instance associated with the Priority Matrix record. |
Instance_Text | String | "Info" | Display text of the associated instance. |
Business Use Cases
Scenario | Resolution |
|---|---|
An integration must calculate Incident Priority from Impact and Urgency. | Retrieve the Priority Matrix records, locate the mapping with the matching Impact and Urgency values, and use the returned Priority identifier in the Incident request. |
An administrator needs to review Priority calculations. | Retrieve all mappings to verify which Priority each Impact and Urgency combination assigns. |
An integration must check an automatically calculated Priority. | Compare the Incident's Impact, Urgency, and Priority with the corresponding active Priority Matrix record. |
An external system stores Priority Matrix mappings. | Retrieve the latest records and synchronize them with the external system's mapping table. |
A scheduled integration must keep Priority reference data up to date. | Call the API at scheduled intervals and compare the response with the mappings stored in the consuming system. |
An integration must avoid using an inactive mapping. | Confirm that the matching record has Active set to true before using its Priority value. |
A reporting system needs readable Priority labels. | Use Priority_Text or Priority_Text_Display to show the configured Priority name in reports and exports. |
An integration supports many application instances. | Use Instance and Instance_Text to associate each Priority Matrix record with the correct instance during synchronization or Incident processing. |
You are migrating Incident data from another system. | Retrieve the configured matrix and map the source system's Impact, Urgency, and Priority values to the corresponding target-system identifiers before migration. |
Expected Result
Returns HTTP 200 OK.
Returns all available Priority Matrix master records configured for Incident Management.
Returns each record's unique ID, active status, Impact, Urgency, resulting Priority, display labels, and instance information.
Sample Expected Result
The API successfully retrieves the configured Priority Matrix records for Incident Management.
[
{
"UID": 1001,
"Active": true,
"Impact": 1,
"Impact_Text": "High",
"Urgency": 1,
"Urgency_Text": "High",
"Priority": 1,
"Priority_Text": "Critical",
"Priority_Text_Display": "P1 - Critical",
"Instance": "Info",
"Instance_Text": "Info"
}
]
Retrieve Priority Matrix Master Record Details
This endpoint retrieves a specific Priority Matrix master record by using its unique record ID. Use this operation when an integration or automated process already knows the record ID and needs to verify the corresponding Impact, Urgency, Priority, active status, or instance information.
Endpoint
GET /API/v1/Master/IM/PriorityMatrix/{recordId}
Component | Value | Description |
|---|---|---|
HTTP Method | GET | Retrieves data from the server. This is a read-only operation, update, or delete records. |
API | API | Stands for Application Programming Interface . It provides a standard way for applications to communicate with the system and exchange data. |
Version | v1 | Indicates Version 1 of the API. |
Resource Group | Master | Refers to the Master Data module. |
Module | IM | Stands for Incident Management . |
Resource | PriorityMatrix | Specifies the Priority Matrix master data resource. |
Record Identifier | {recordId} | Unique identifier of the Priority Matrix record to retrieve. Replace this placeholder with an actual record ID, such as 1001. |
Path Parameter
Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
recordId | Integer | Yes | Unique identifier of the Priority Matrix master record. | 1001 |
Request Headers
{
"Accept": "application/json",
"X-Api-Key": "<API_KEY>"
}
Header | Value | Required | Description |
|---|---|---|---|
Accept | application/json | Yes | Requests the API to return the response in JSON format. |
X-Api-Key | <API_KEY> | Yes | Provide the API key to authenticate the caller and grant access to the endpoint. |
Sample Request
The following request retrieves the Priority Matrix record with the record ID 1001. Replace 1001 with the required record ID, <API_KEY> with a valid API key, and http://localhost:57757 with the appropriate server address.
curl --location 'http://localhost:57757/API/v1/Master/IM/PriorityMatrix/1001' \
--request GET \
--header 'Accept: application/json' \
--header 'X-Api-Key: <API_KEY>'
Sample Response
The response returns the Priority Matrix record whose UID matches the record ID specified in the request URL.
{
"UID": 1001,
"Active": true,
"Impact": 1,
"Impact_Text": "High",
"Urgency": 1,
"Urgency_Text": "High",
"Priority": 1,
"Priority_Text": "Critical",
"Priority_Text_Display": "P1 - Critical",
"Instance": "Info",
"Instance_Text": "Info"
}
In this example, the record maps High Impact and High Urgency to the Critical Priority. The Active value confirms that the mapping is available for use, while Instance and Instance_Text identify the associated application instance.
Field | Value | Description |
|---|---|---|
UID | 1001 | Uniquely identifies the Priority Matrix record. |
Active | true | Indicates that the mapping is active and available for use. |
Impact | 1 | Identifies the mapped Impact value. |
Impact_Text | High | Displays the name of the mapped Impact value. |
Urgency | 1 | Identifies the mapped Urgency value. |
Urgency_Text | High | Displays the name of the mapped Urgency value. |
Priority | 1 | Identifies the resulting Priority value. |
Priority_Text | Critical | Displays the name of the resulting Priority. |
Priority_Text_Display | P1 - Critical | Provides the formatted display name of the resulting Priority. |
Instance | Info | Provides the associated instance identifier or value. |
Instance_Text | Info | Provides the display text of the associated instance. |
Note
This endpoint describes the configured mapping. It does not update an Incident or recalculate its Priority by itself. An integration can use the returned values to check or apply Priority logic in a separate Incident operation.
Business Use Cases
Scenario | Resolution |
|---|---|
An external system receives a Priority Matrix record ID. | Retrieve the specific record to get its Impact, Urgency, and Priority mapping before processing the Incident. |
An integration must verify a calculated Priority. | Retrieve the record and compare its Impact, Urgency, and Priority values with the Incident data. |
A synchronization process detects that one mapping has changed. | Retrieve only the affected record and update its mapping in the target system without retrieving the complete matrix. |
An automated workflow must confirm that a mapping is active. | Retrieve the record and check that Active is true before continuing. |
A reporting system stores a Priority Matrix UID but not its descriptive labels. | Retrieve the record and use Impact_Text, Urgency_Text, and Priority_Text_Display in reports or exported data. |
A mapping fails during Incident processing. | Retrieve the record by UID and compare the returned values with the mapping stored in the external system to identify the mismatch. |
An integration supports many instances. | Retrieve the record and use Instance and Instance_Text to confirm that it belongs to the intended instance. |
Expected Result
Returns HTTP 200 OK.
Returns the Priority Matrix master record that matches the specified recordId.
Returns the record ID, active status, Impact, Urgency, resulting Priority, display labels, and instance information.
Sample Expected Result
The API successfully retrieves the Priority Matrix record with the record ID 1001.
{
"UID": 1001,
"Active": true,
"Impact": 1,
"Impact_Text": "High",
"Urgency": 1,
"Urgency_Text": "High",
"Priority": 1,
"Priority_Text": "Critical",
"Priority_Text_Display": "P1 - Critical",
"Instance": "Info",
"Instance_Text": "Info"
}
Error Responses
401 Unauthorized
Returned when the request does not include a valid API key or the caller does not have authenticated access.
The following request does not include the required X-Api-Key header:
curl --location '{host}/API/v1/Master/IM/PriorityMatrix' \
--request GET \
--header 'Accept: application/json'
{
"message": "Unauthorized",
"errorCode": 401,
"details": "Valid API credentials are required."
}
404 Not Found
Returned when the requested Priority Matrix record ID does not exist or the endpoint path is incorrect.
The following request attempts to retrieve a Priority Matrix record with the record ID 9999:
curl --location '{host}/API/v1/Master/IM/PriorityMatrix/9999' \
--request GET \
--header 'Accept: application/json' \
--header 'X-Api-Key: {API_KEY}'
{
"message": "Record not found",
"errorCode": 404,
"details": "The requested Priority Matrix record was not found."
}