Delete a specific incident_sub_status by id
curl --request DELETE \
--url https://api.rootly.com/v1/incident_sub_statuses/{id} \
--header 'Authorization: Bearer <token>'{
"data": {
"id": "94481e80-31bf-475c-8257-31f77523e91b",
"type": "incident_sub_statuses",
"attributes": {
"sub_status_id": "354060c8-449b-48b7-bab8-c85122da5e8c",
"incident_id": "c27e955d-de83-4d32-9103-281d9d4de568",
"assigned_at": "2025-12-16T13:17:05.846-08:00",
"assigned_by_user_id": 359
},
"relationships": {
"sub_status": {
"data": {
"id": "354060c8-449b-48b7-bab8-c85122da5e8c",
"type": "sub_statuses"
}
},
"assigned_by_user": {
"data": {
"id": "359",
"type": "users"
}
}
}
}
}Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
incident_sub_status deleted
Show child attributes
Unique ID of the incident_sub_status
incident_sub_statuses Show child attributes
Note: To change an incident's sub-status, use the PATCH /incidents/:id endpoint and set the sub_status_id attribute. This endpoint is for modifying the timestamp of when an incident's sub-status was assigned.
Was this page helpful?
curl --request DELETE \
--url https://api.rootly.com/v1/incident_sub_statuses/{id} \
--header 'Authorization: Bearer <token>'{
"data": {
"id": "94481e80-31bf-475c-8257-31f77523e91b",
"type": "incident_sub_statuses",
"attributes": {
"sub_status_id": "354060c8-449b-48b7-bab8-c85122da5e8c",
"incident_id": "c27e955d-de83-4d32-9103-281d9d4de568",
"assigned_at": "2025-12-16T13:17:05.846-08:00",
"assigned_by_user_id": 359
},
"relationships": {
"sub_status": {
"data": {
"id": "354060c8-449b-48b7-bab8-c85122da5e8c",
"type": "sub_statuses"
}
},
"assigned_by_user": {
"data": {
"id": "359",
"type": "users"
}
}
}
}
}