The POST Urgency Incident Master API creates a new Urgency master record in the Incident Management (IM) module. Authorized administrators, integrations, and automation tools can create Urgency records without using the application UI.
Endpoint
POST /API/v1/Master/IM/Urgency
Path Details
Path Value | Description |
|---|---|
| Module code for Incident Management. |
| Master entity in which the API creates the new record. |
Note: Before creating an Urgency record, system retrieves its metadata to review required fields, supported fields, payload structure, constraints, and applicable endpoints.
GET /API/v1/Master/IM/Urgency/metadata?sections=create.
Sample Metadata Request
curl --location 'https://<host>/API/v1/Master/IM/Urgency/metadata?sections=create' \
--request GET \
--header 'Accept: application/json' \
--header 'X-Api-Key: <API_KEY>'
Request Headers
Header | Value | Required | Description |
|---|---|---|---|
|
| Yes | Specifies the expected response format. |
|
| Yes | Specifies that the request body is in JSON format. |
|
| Yes | API key used to authenticate the request. |
Request Body Fields
Field | Data Type | Required | Description |
|---|---|---|---|
| Boolean | No | Indicates whether the Urgency record is active. |
| String | Yes | Display name or text value of the Urgency record. |
| Boolean | No | Indicates whether the Urgency is the default value. |
| Integer | No | Defines the display or processing order of the Urgency record. |
| String | No | Instance or tenant associated with the Urgency record. |
Sample Payload
{
"Active": true,
"Text": "Sample Urgency Name",
"Is_Default": false,
"Sort_Order": 0,
"Instance": "Info"
}
Sample Payload Field Details
Field Name | Sample Value | Data Type | Description |
|---|---|---|---|
Active |
| Boolean | Indicates whether the Urgency record is active and available for use. |
Text |
| String | Specifies the display name of the Urgency record. |
Is_Default |
| Boolean | Indicates whether the Urgency acts as the default Urgency value. |
Sort_Order |
| Integer | Specifies the display or processing order of the Urgency record. |
Instance |
| String | Specifies the application instance associated with the Urgency record. |
Sample Payload Explanation
Attribute | Value | Explanation |
|---|---|---|
Active Status |
| Creates the Urgency as an active record that is available for use. |
Urgency Name |
| Sets the display name of the new Urgency record. |
Default Status |
| Creates the Urgency as a non-default Urgency value. |
Sort Order |
| Sets the display or processing order of the Urgency record to |
Application Instance |
| Associates the Urgency record with the specified application instance. |
Note: While creating a Default Urgency by setting Is_Default: true, only one default Urgency must exist, setting more than one will return error.
Sample Request
curl --location 'https://<host>/API/v1/Master/IM/Urgency' \
--request POST \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--header 'X-Api-Key: <API_KEY>' \
--data-raw '{
"Active": true,
"Text": "Sample Urgency Name",
"Is_Default": false,
"Sort_Order": 0,
"Instance": "Info"
}'
Sample Request Details
Component | Value | Description |
|---|---|---|
HTTP Method |
| Creates a new Urgency master record. |
Endpoint URL |
| API endpoint used to create an Urgency record. |
Host |
| Base URL of the target environment, such as Development, Test, or Production. |
API Version |
| Identifies Version 1 of the API. |
Resource Group |
| Identifies the Master Data API resource group. |
Module |
| Identifies the Incident Management module. |
Master Name |
| Identifies the Urgency master entity. |
Accept Header |
| Indicates that the client expects the response in JSON format. |
Content-Type Header |
| Indicates that the request body contains JSON data. |
X-Api-Key Header |
| API key used to authenticate and approve the request. |
Request Body | JSON payload | Contains the values used to create the Urgency record. |
Request Body Details
Field Name | Sample Value | Data Type | Required | Description |
|---|---|---|---|---|
Active |
| Boolean | Yes | Creates the Urgency as an active record that is available for use. |
Text |
| String | Yes | Sets the display name of the Urgency record. |
Is_Default |
| Boolean | Yes | Specifies that the Urgency is not the default Urgency value. |
Sort_Order |
| Integer | Yes | Sets the display or processing order of the Urgency record. |
Instance |
| String | Yes | Associates the Urgency with the specified application instance. |
Sample Request Explanation
Attribute | Submitted Value | Result |
|---|---|---|
HTTP Operation |
| Requests the creation of a new Urgency record. |
Urgency Name |
| Creates the Urgency with the specified display name. |
Active Status |
| Makes the new Urgency active and available for use. |
Default Status |
| Does not configure the new Urgency as the default Urgency value. |
Sort Order |
| Assigns the display or processing order |
Application Instance |
| Associates the new Urgency record with the specified application instance. |
The request creates an active Urgency record named Sample Urgency Name, does not set the record as the default Urgency, assigns a sort order of 0, and associates the record with the specified application instance.
Sample Success Response
HTTP 201 Created
{
"message": "Master record created successfully.",
"data": {
"success": true,
"recordId": 17,
"displayName": "Urgency",
"moduleCode": "IM",
"operation": "INSERT",
"rowsAffected": 1
},
"executionTime": 0.0553389
}
A successful request creates the Urgency record and returns the generated record identifier and execution details.
Sample Success Response Field Details
Field Name | Sample Value | Data Type | Description |
|---|---|---|---|
message |
| String | Confirms that the system created the Urgency record successfully. |
data | Response object | Object | Contains details about the completed create operation. |
data.success |
| Boolean | Indicates whether the Urgency create operation succeeded. |
data.recordId |
| Integer | Unique identifier generated for the newly created Urgency record. |
data.displayName |
| String | Identifies the master entity the system created. |
data.moduleCode |
| String | Identifies the Incident Management module associated with the new record. |
data.operation |
| String | Indicates that the API performed an insert operation. |
data.rowsAffected |
| Integer | Indicates the number of Urgency records created by the request. |
executionTime |
| Number | Indicates the time taken to process the request, in seconds. |
Sample Success Response Explanation
Response Attribute | Returned Value | Meaning |
|---|---|---|
HTTP Status |
| Indicates that the API successfully created a new resource. |
Response Message |
| Confirms that the system completed the Urgency creation operation successfully. |
Operation Status |
| Confirms that the system created the Urgency record successfully. |
Generated Record ID |
| Identifies the newly created Urgency record. |
Master Entity |
| Confirms that the created record belongs to the Urgency master. |
Module |
| Confirms that the record belongs to the Incident Management module. |
Operation |
| Confirms that the API performed a create operation. |
Rows Affected |
| Confirms that the system created one Urgency record. |
Execution Time |
| Reports the time taken to process the create request. |
A successful request returns HTTP 201 Created. The response confirms that the system created a new Urgency record, the generated record ID is 17, and the request affected one record.
Error Responses
400 Bad Request
{
"message": "Invalid request payload.",
"errorCode": 400,
"details": "One or more fields failed validation."
}
401 Unauthorized
{
"message": "Unauthorized access.",
"errorCode": 401,
"details": "Valid API credentials are required."
}
403 Forbidden
{
"message": "You do not have permission to create master records.",
"errorCode": 403,
"details": "The authenticated user lacks the required privileges to perform this operation."
}
404 Not Found
{
"message": "Master entity not found.",
"errorCode": 404,
"details": "The requested master entity or endpoint does not exist."
}