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": "39eb7da2-e689-4f58-8904-47fdde6d999e",
"type": "incident_sub_statuses",
"attributes": {
"sub_status_id": "420d6b93-7309-465d-b229-a69d6496d18e",
"incident_id": "c61554f0-a2eb-4392-a686-96d4a6df5e70",
"assigned_at": "2025-09-03T17:43:15.903-07:00",
"assigned_by_user_id": 313
},
"relationships": {
"sub_status": {
"data": {
"id": "420d6b93-7309-465d-b229-a69d6496d18e",
"type": "sub_statuses"
}
},
"assigned_by_user": {
"data": {
"id": "313",
"type": "users"
}
}
}
}
}
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
incident_sub_status deleted
The response is of type object
.
Was this page helpful?
curl --request DELETE \
--url https://api.rootly.com/v1/incident_sub_statuses/{id} \
--header 'Authorization: Bearer <token>'
{
"data": {
"id": "39eb7da2-e689-4f58-8904-47fdde6d999e",
"type": "incident_sub_statuses",
"attributes": {
"sub_status_id": "420d6b93-7309-465d-b229-a69d6496d18e",
"incident_id": "c61554f0-a2eb-4392-a686-96d4a6df5e70",
"assigned_at": "2025-09-03T17:43:15.903-07:00",
"assigned_by_user_id": 313
},
"relationships": {
"sub_status": {
"data": {
"id": "420d6b93-7309-465d-b229-a69d6496d18e",
"type": "sub_statuses"
}
},
"assigned_by_user": {
"data": {
"id": "313",
"type": "users"
}
}
}
}
}