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": "fd77f702-955a-442b-a7ff-dc6ecde5fa8d",
"type": "incident_sub_statuses",
"attributes": {
"sub_status_id": "64bfcf10-5113-4f85-a4d5-1f01f0138349",
"incident_id": "de9fcfed-d96d-42f4-ad7b-b1e2fdaba745",
"assigned_at": "2025-12-05T21:26:39.203-08:00",
"assigned_by_user_id": 359
},
"relationships": {
"sub_status": {
"data": {
"id": "64bfcf10-5113-4f85-a4d5-1f01f0138349",
"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": "fd77f702-955a-442b-a7ff-dc6ecde5fa8d",
"type": "incident_sub_statuses",
"attributes": {
"sub_status_id": "64bfcf10-5113-4f85-a4d5-1f01f0138349",
"incident_id": "de9fcfed-d96d-42f4-ad7b-b1e2fdaba745",
"assigned_at": "2025-12-05T21:26:39.203-08:00",
"assigned_by_user_id": 359
},
"relationships": {
"sub_status": {
"data": {
"id": "64bfcf10-5113-4f85-a4d5-1f01f0138349",
"type": "sub_statuses"
}
},
"assigned_by_user": {
"data": {
"id": "359",
"type": "users"
}
}
}
}
}