The GET Impact Incident Master API retrieves Impact master data from the Incident Management (IM) module. The API response matches the Impact records displayed in the UI.
The API supports the following operations:
Retrieve List of Impact Master Records
This endpoint retrieves all Impact master records configured in the Incident Management module. Administrators, integrations, and automation tools can use the endpoint for configuration review, validation, reporting, and downstream processing.
Endpoint
GET /API/v1/Master/IM/Impact
Component | Value | Description |
|---|---|---|
HTTP Method | GET | Retrieves data from the server. This operation reads data only and does not create, 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 Impacts, Categories, Priorities, Statuses, and Locations. |
Module | IM | Stands for Incident Management. It identifies that the requested master data belongs to the Incident Management module. |
Resource | Impact | Specifies the Impact master data resource to retrieve. Impact values describe the extent to which an Incident affects users, services, or business operations. |
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 |
| Yes | API key for authentication and authorization. |
Sample Request
The following cURL request sends an HTTP GET request to retrieve all Impact master records. The request includes the Accept header to specify JSON as the expected response format and the X-Api-Key header to authenticate the caller.
Replace <API_KEY> with a valid API key before sending the request. Replace http://localhost:57757 with the appropriate server address when calling the API from another environment.
curl --location 'http://localhost:57757/API/v1/Master/IM/Impact' \
--request GET \
--header 'Accept: application/json' \
--header 'X-Api-Key: <API_KEY>'
Sample Response
The following sample response returns an array of Impact master records. Each object is an Impact in the Incident Management module. Value uniquely identifies the record, Text provides its display name, Active indicates availability, and Sort_Order defines its display or processing sequence.
[
{
"Value": 1,
"Text": "High",
"Active": true,
"Sort_Order": 1,
"Instance": 1,
"Instance_Text": "Production"
},
{
"Value": 2,
"Text": "Medium",
"Active": true,
"Sort_Order": 2,
"Instance": 1,
"Instance_Text": "Production"
}
]
Note: The sample values are illustrative. Actual values depend on the Impact records and instances configured in the tenant.
Response Fields
The Impact master list exposes the following fields:
Field | Type | Example Value | Description |
|---|---|---|---|
Value | Integer | 1 | Unique value or identifier of the Impact record. |
Text | String |
| Display name of the Impact. |
Active | Boolean |
| Indicates whether the Impact record is active and available for use. |
Sort_Order | Integer | 1 | Defines the display or processing order of the Impact record. A lower value generally places the record earlier in the configured sequence. |
Instance | Integer or String | 1 | Identifier of the instance associated with the Impact. |
Instance_Text | String |
| Display name of the instance associated with the Impact. |
Business Use Cases
Scenario | Resolution |
|---|---|
An integration needs valid Impact values before creating or updating an Incident. | Call the GET Impact Incident Master API to retrieve the configured Impact records. Use the returned Impact identifier in the Incident create or update request. |
An external system stores Impact mappings for Incident synchronization. | Call the API to retrieve the latest Impact master records and synchronize them with the external system's mapping table. |
An automated process receives an Impact name but requires its unique identifier. | Retrieve the Impact master list, locate the record with the matching Impact name, and use its |
A scheduled integration must keep Impact reference data up to date. | Call the API at scheduled intervals and compare the response with the Impact records stored in the consuming system. Add, update, or deactivate mappings as required. |
An integration must verify an Impact before submitting an Incident request. | Call the API and confirm that the Impact exists and that its |
An integration must preserve the configured Impact sequence. | Use |
You are migrating Incident data from another system. | Retrieve all valid Impact records and map the source-system Impact values to the corresponding Impact identifiers before migrating the Incident records. |
An integration supports many application instances. | Use the |
Expected Result
Returns HTTP 200 OK.
Returns all available Impact master records configured for Incident Management.
Returns details for each Impact, including its identifier, display name, active status, sort order, and instance information.
Sample Expected Result
The API successfully retrieves the list of Impact master records configured for Incident Management.
[
{
"Value": 1,
"Text": "High",
"Active": true,
"Sort_Order": 1,
"Instance": 1,
"Instance_Text": "Production"
},
{
"Value": 2,
"Text": "Medium",
"Active": true,
"Sort_Order": 2,
"Instance": 1,
"Instance_Text": "Production"
}
]
Retrieve Impact Master Record Details
This endpoint retrieves the details of a specific Impact master record by using its unique record ID.
Endpoint
GET /API/v1/Master/IM/Impact/{recordId}
Component | Value | Description |
|---|---|---|
HTTP Method | GET | Retrieves data from the server. This operation reads data only and does not create, 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 introducing new API versions. |
Resource Group | Master | Refers to the Master Data module, which contains reusable reference data. |
Module | IM | Stands for Incident Management. It identifies that the requested master data belongs to the Incident Management module. |
Resource | Impact | Specifies the Impact master data resource to retrieve. |
Record Identifier |
| The unique identifier of the Impact record to retrieve. Replace this placeholder with an actual record ID, such as |
Path Parameter
Parameter | Type | Required | Description |
|---|---|---|---|
recordId | Integer | Yes | Unique identifier of the Impact master record. |
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 |
| Yes | Provides the API key to authenticate the caller and grant access to the endpoint. |
Sample Request
The following request retrieves the Impact master record with the record ID 1. Supply recordId as a path parameter in the endpoint URL to identify the specific Impact record.
Use this request when an integration or automated process needs the configuration details of a known Impact record. Replace 1 with the record ID of the Impact that you want to retrieve. Replace <API_KEY> with a valid API key. Replace http://localhost:57757 with the appropriate server address when calling the API from another environment.
curl --location 'http://localhost:57757/API/v1/Master/IM/Impact/1' \
--request GET \
--header 'Accept: application/json' \
--header 'X-Api-Key: <API_KEY>'
Sample Response
The response returns the Impact master record whose Value matches the record ID specified in the request URL.
{
"Value": 1,
"Text": "High",
"Active": true,
"Sort_Order": 1,
"Instance": 1,
"Instance_Text": "Production"
}
In this example, the API returns the Impact named High with the following configuration:
Field | Value | Description |
|---|---|---|
Value | 1 | Uniquely identifies the Impact record. |
Text | High | Specifies the display name of the Impact. |
Active |
| Indicates that the Impact is active and available for use. |
Sort_Order | 1 | Specifies the configured display or processing position of the Impact. |
Instance | 1 | Identifies the application instance associated with the Impact. |
Instance_Text | Production | Provides the display name of the associated application instance. |
An integration can use these values to verify the Impact configuration before using its identifier in another Incident Management API request.
Note
The
Activefield shows whether the Impact is available for use. TheSort_Orderfield describes its configured sequence. TheInstanceandInstance_Textfields identify the associated application instance.
Use this response when you need the details of a specific Impact record, such as verifying its active status, configured order, or instance association for a known record ID.
Business Use Cases
Scenario | Resolution |
|---|---|
An external system receives an Incident that contains an Impact record ID. | Retrieve the specific Impact record to get its name and configuration before processing or synchronizing the Incident. |
An integration must check an Impact before creating or updating an Incident. | Retrieve the Impact by |
A synchronization process detects that one Impact record has changed. | Retrieve only the affected Impact record and update its mapping in the target system without retrieving the complete Impact master list. |
An Incident imported from another system contains an existing Impact mapping. | Retrieve the mapped Impact record to confirm that the stored record ID still corresponds to the expected Impact. |
An automated workflow must apply rules based on an Impact's configuration. | Retrieve the Impact record and check its active status, sort order, and instance information before continuing the workflow. |
A reporting system contains an Incident Impact ID but not its descriptive name. | Retrieve the Impact record and use its |
An integration must determine the configured position of a known Impact. | Retrieve the Impact record and check |
An Impact mapping fails during Incident processing. | Retrieve the Impact using the mapped |
Expected Result
Returns HTTP 200 OK.
Returns the Impact master record that matches the specified
recordId.Returns the Impact identifier, display name, active status, sort order, and instance information.
Sample Expected Result
The API successfully retrieves the Impact record with the record ID 1.
{
"Value": 1,
"Text": "High",
"Active": true,
"Sort_Order": 1,
"Instance": 1,
"Instance_Text": "Production"
}
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/Impact' \
--request GET \
--header 'Accept: application/json'
{
"message": "Unauthorized",
"errorCode": 401,
"details": "Valid API credentials are required."
}
404 Not Found
Returned when the requested Impact record ID does not exist or the endpoint path is incorrect.
The following request attempts to retrieve an Impact record with the record ID 9999:
curl --location '{host}/API/v1/Master/IM/Impact/9999' \
--request GET \
--header 'Accept: application/json' \
--header 'X-Api-Key: {API_KEY}'
{
"message": "Record not found",
"errorCode": 404,
"details": "The requested Impact record was not found."
}