Resource

Incident Severity

Manage incident severity for your project (Created, Acknowledged for example). Add / edit or remove severities.

The Incident Severity Model

Properties

Name
_id
Type
Object ID
Description
ID of this object
Name
createdAt
Type
Date
Description
Date and Time when the object was created.
Name
updatedAt
Type
Date
Description
Date and Time when the object was updated.
Name
project
Type
Project
Description
Relation to Project Resource in which this object belongs
Name
projectId
Type
Object IDRequired
Description
ID of your Project in which this object belongs
Name
name
Type
TextRequired
Description
Any friendly name of this object
Name
slug
Type
SlugRequired
Description
Friendly globally unique name for your object
Name
description
Type
Long Text
Description
Friendly description that will help you remember
Name
createdByUser
Type
User
Description
Relation to User who created this object (if this object was created by a User)
Name
createdByUserId
Type
Object ID
Description
User ID who created this object (if this object was created by a User)
Name
color
Type
ColorRequired
Description
Color of this resource in Hex (#32a852 for example)
Name
order
Type
Small Number
Description
Order / Priority of this resource

GETorPOST/api/incident-severity/get-list

List

This endpoint allows you to retrieve a paginated list of all your Incident Severity. By default, a maximum of ten Incident Severity are shown per page.

Optional Query Params

limit
number
Number of objects to fetch. By default 10, you can increase this count up to 100
skip
number
Number of objects to skip. This can be useful in pagination

Optional Request Body

query
If you would like to filter on Incident Severity. You can specify include a query here. For more information, please check out writing queries here.
select
By default you will only retrieve ID of objects, to retrieve more fields you need to select them. For more information, please check how to select here.
sort
Objects will be sorted based on created date by default. You can change the sort order — see Data Types: Sort.

List Request

POST

/api/incident-severity/get-list?skip=0&limit=10

Headers

Content-Type: application/json
ApiKey: YOUR_API_KEY

Body

{
  "select": {
    "name": true,
    "projectId": true,
    "description": true,
    "color": true,
    "slug": true
  },
  "query": {
    "name": "Critical"
  },
  "sort": {
    "createdAt": -1
  }
}

Response

{
  "count": 10,
  "limit": 10,
  "skip": 0,
  "data": [
    {
      "_id": "377206e0-28fe-11f1-b591-3fdcef396aba",
      "name": "Critical",
      "projectId": "5f8b9c0d-e1a2-4b3c-8d5e-6f7a8b9c0d1e",
      "description": "Critical severity incidents require immediate attention and response from on-call engineers",
      "color": "#3498db",
      "slug": "Example slug"
    },
    {
      "_id": "377206e1-28fe-11f1-b591-3fdcef396aba",
      "name": "Critical",
      "projectId": "5f8b9c0d-e1a2-4b3c-8d5e-6f7a8b9c0d1e",
      "description": "Critical severity incidents require immediate attention and response from on-call engineers",
      "color": "#3498db",
      "slug": "Example slug"
    },
    {
      "_id": "377206e2-28fe-11f1-b591-3fdcef396aba",
      "name": "Critical",
      "projectId": "5f8b9c0d-e1a2-4b3c-8d5e-6f7a8b9c0d1e",
      "description": "Critical severity incidents require immediate attention and response from on-call engineers",
      "color": "#3498db",
      "slug": "Example slug"
    }
  ]
}

GETorPOST/api/incident-severity/:id/get-item

Get item by ID

This endpoint allows you to retrieve Incident Severity by ID.

id
text
ID of the Object

Optional Request Body

select
By default you will only retrieve ID of objects, to retrieve more fields you need to select them. For more information, please check how to select here.

Get Item Request

POST

/api/incident-severity/:id/get-item

Headers

Content-Type: application/json
ApiKey: YOUR_API_KEY

Body

{
  "select": {
    "name": true,
    "projectId": true,
    "description": true,
    "color": true,
    "slug": true
  }
}

Response

{
  "_id": "377206e0-28fe-11f1-b591-3fdcef396aba",
  "name": "Critical",
  "projectId": "5f8b9c0d-e1a2-4b3c-8d5e-6f7a8b9c0d1e",
  "description": "Critical severity incidents require immediate attention and response from on-call engineers",
  "color": "#3498db",
  "slug": "Example slug"
}

POST/api/incident-severity/count

Count

This endpoint allows you to retrieve the count of all your Incident Severity.

Optional Request Body

query
If you would like to filter on Incident Severity. You can specify include a query here. For more information, please check out writing queries here.

Count Request

POST

/api/incident-severity/count

Headers

Content-Type: application/json
ApiKey: YOUR_API_KEY

Body

{
  "query": {
    "name": "Critical"
  }
}

Response

{
  "count": 107
}

POST/api/incident-severity

Create Incident Severity

This endpoint allows you to create a new object.

Create Request

POST

/api/incident-severity

Headers

Content-Type: application/json
ApiKey: YOUR_API_KEY

Body

{
  "data": {
    "name": "Critical",
    "projectId": "5f8b9c0d-e1a2-4b3c-8d5e-6f7a8b9c0d1e",
    "description": "Critical severity incidents require immediate attention and response from on-call engineers",
    "color": "#3498db",
    "createdByUser": "Example created by user"
  }
}

Response

{
  "_id": "377206e0-28fe-11f1-b591-3fdcef396aba",
  "name": "Critical",
  "projectId": "5f8b9c0d-e1a2-4b3c-8d5e-6f7a8b9c0d1e",
  "description": "Critical severity incidents require immediate attention and response from on-call engineers",
  "color": "#3498db",
  "slug": "Example slug"
}

PUT/api/incident-severity/:id

Update by ID

This endpoint allows you to update object by its ID.

Alternative Methods

For clients that do not support PUT requests, you can use POST or GET with the same request headers and body:

POST/api/incident-severity/:id/update-item

GET/api/incident-severity/:id/update-item

Update Request

PUT

/api/incident-severity/:id

Headers

Content-Type: application/json
ApiKey: YOUR_API_KEY

Body

{
  "data": {
    "name": "Critical",
    "description": "Critical severity incidents require immediate attention and response from on-call engineers",
    "color": "#3498db"
  }
}

Response

{}

DELETE/api/incident-severity/:id

Delete by ID

This endpoint allows you to delete object by its ID.

Alternative Methods

For clients that do not support DELETE requests, you can use POST or GET with the same request headers and body:

POST/api/incident-severity/:id/delete-item

GET/api/incident-severity/:id/delete-item

Delete Request

DELETE

/api/incident-severity/:id

Headers

Content-Type: application/json
ApiKey: YOUR_API_KEY

Response

{}

Permissions

Your API Token needs permissions to create, update, read or delete this resource. If you do not have permissions to make a request a 4xx status will be sent as response.

Read Permissions

Required to read Incident Severity

Project Owner
Project Admin
Project Member
Read Incident Severity
Read All Project Resources

Create Permissions

Required to create Incident Severity

Project Owner
Project Admin
Project Member
Create Incident Severity

Update Permissions

Required to update Incident Severity

Project Owner
Project Admin
Project Member
Edit Incident Severity

Delete Permissions

Required to delete Incident Severity

Project Owner
Project Admin
Project Member
Delete Incident Severity