Incident Member
Assign users with specific roles to incidents.
The Incident Member 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 Status200 Project in which this object belongs
- Name
user- Type
- User
- Description
User assigned to the incident with a specific role.
- Name
userId- Type
- Object IDRequired
- Description
ID of your Status200 User in which this object belongs
- Name
incident- Type
- Incident
- Description
Relation to Incident Resource in which this object belongs
- Name
incidentId- Type
- Object IDRequired
- Description
ID of your Status200 Incident in which this object belongs
- Name
incidentRole- Type
- Incident Role
- Description
The role assigned to the user for this incident
- Name
incidentRoleId- Type
- Object IDRequired
- Description
ID of the Incident Role assigned to this user
- Name
notes- Type
- Long Text
- Description
Assignment context or notes
- 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)
/api/incident-member/get-listList
This endpoint allows you to retrieve a paginated list of all your Incident Member. By default, a maximum of ten Incident Member 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 Member. 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-member/get-list?skip=0&limit=10Content-Type: application/json ApiKey: YOUR_API_KEY
{
"select": {
"incidentId": true,
"incidentRoleId": true,
"projectId": true,
"userId": true,
"createdByUser": true
},
"query": {
"notes": "Primary responder for this incident"
},
"sort": {
"createdAt": -1
}
}Response
{
"count": 10,
"limit": 10,
"skip": 0,
"data": [
{
"_id": "37711c80-28fe-11f1-b591-3fdcef396aba",
"incidentId": "f6a7b8c9-d0e1-2345-fabc-456789012345",
"incidentRoleId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"projectId": "5f8b9c0d-e1a2-4b3c-8d5e-6f7a8b9c0d1e",
"userId": "e5f6a7b8-c9d0-1234-efab-345678901234",
"createdByUser": "c3d4e5f6-a7b8-9012-cdef-123456789012"
},
{
"_id": "37711c81-28fe-11f1-b591-3fdcef396aba",
"incidentId": "f6a7b8c9-d0e1-2345-fabc-456789012345",
"incidentRoleId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"projectId": "5f8b9c0d-e1a2-4b3c-8d5e-6f7a8b9c0d1e",
"userId": "e5f6a7b8-c9d0-1234-efab-345678901234",
"createdByUser": "c3d4e5f6-a7b8-9012-cdef-123456789012"
},
{
"_id": "37711c82-28fe-11f1-b591-3fdcef396aba",
"incidentId": "f6a7b8c9-d0e1-2345-fabc-456789012345",
"incidentRoleId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"projectId": "5f8b9c0d-e1a2-4b3c-8d5e-6f7a8b9c0d1e",
"userId": "e5f6a7b8-c9d0-1234-efab-345678901234",
"createdByUser": "c3d4e5f6-a7b8-9012-cdef-123456789012"
}
]
}/api/incident-member/:id/get-itemGet item by ID
This endpoint allows you to retrieve Incident Member 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-member/:id/get-itemContent-Type: application/json ApiKey: YOUR_API_KEY
{
"select": {
"incidentId": true,
"incidentRoleId": true,
"projectId": true,
"userId": true,
"createdByUser": true
}
}Response
{
"_id": "37711c80-28fe-11f1-b591-3fdcef396aba",
"incidentId": "f6a7b8c9-d0e1-2345-fabc-456789012345",
"incidentRoleId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"projectId": "5f8b9c0d-e1a2-4b3c-8d5e-6f7a8b9c0d1e",
"userId": "e5f6a7b8-c9d0-1234-efab-345678901234",
"createdByUser": "c3d4e5f6-a7b8-9012-cdef-123456789012"
}/api/incident-member/countCount
This endpoint allows you to retrieve the count of all your Incident Member.
Optional Request Body
query- If you would like to filter on Incident Member. You can specify include a query here. For more information, please check out writing queries here.
Count Request
POST/api/incident-member/countContent-Type: application/json ApiKey: YOUR_API_KEY
{
"query": {
"notes": "Primary responder for this incident"
}
}Response
{
"count": 107
}/api/incident-memberCreate Incident Member
This endpoint allows you to create a new object.
Create Request
POST/api/incident-memberContent-Type: application/json ApiKey: YOUR_API_KEY
{
"data": {
"incidentId": "f6a7b8c9-d0e1-2345-fabc-456789012345",
"incidentRoleId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"projectId": "5f8b9c0d-e1a2-4b3c-8d5e-6f7a8b9c0d1e",
"userId": "e5f6a7b8-c9d0-1234-efab-345678901234",
"createdByUser": "c3d4e5f6-a7b8-9012-cdef-123456789012"
}
}Response
{
"_id": "37711c80-28fe-11f1-b591-3fdcef396aba",
"incidentId": "f6a7b8c9-d0e1-2345-fabc-456789012345",
"incidentRoleId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"projectId": "5f8b9c0d-e1a2-4b3c-8d5e-6f7a8b9c0d1e",
"userId": "e5f6a7b8-c9d0-1234-efab-345678901234",
"createdByUser": "c3d4e5f6-a7b8-9012-cdef-123456789012"
}/api/incident-member/:idUpdate 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:
Update Request
PUT/api/incident-member/:idContent-Type: application/json ApiKey: YOUR_API_KEY
{
"data": {
"incidentRoleId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"incidentRole": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"notes": "Primary responder for this incident"
}
}Response
{}/api/incident-member/:idDelete 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:
Delete Request
DELETE/api/incident-member/:idContent-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 Member
Project OwnerProject AdminProject MemberRead Incident MemberRead All Project Resources
Create Permissions
Required to create Incident Member
Project OwnerProject AdminProject MemberCreate Incident Member
Update Permissions
Required to update Incident Member
Project OwnerProject AdminProject MemberEdit Incident Member
Delete Permissions
Required to delete Incident Member
Project OwnerProject AdminProject MemberDelete Incident Member