Delete a specific alert routing rule by id
curl --request DELETE \
--url https://api.rootly.com/v1/alert_routing_rules/{id} \
--header 'Authorization: Bearer <token>'
{
"data": {
"id": "a5f2a2fb-71e6-40ff-85c4-8cba00bf64bf",
"type": "alert_routing_rules",
"attributes": {
"name": "Alert Routing Rule 1",
"alerts_source_id": "e637effb-df8f-45a5-8a3b-a4c555e85a61",
"condition_type": "all",
"enabled": false,
"position": 1,
"destination": null,
"created_at": "2025-08-07T22:33:27.751-07:00",
"updated_at": "2025-08-07T22:33:35.227-07:00",
"destinations": [],
"conditions": []
},
"relationships": {
"owning_teams": {
"data": [
{
"id": "ea5650a9-715e-4791-b22a-6bb36939afaf",
"type": "groups"
}
]
}
}
}
}
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
alert routing rule deleted
The response is of type object
.
Was this page helpful?
curl --request DELETE \
--url https://api.rootly.com/v1/alert_routing_rules/{id} \
--header 'Authorization: Bearer <token>'
{
"data": {
"id": "a5f2a2fb-71e6-40ff-85c4-8cba00bf64bf",
"type": "alert_routing_rules",
"attributes": {
"name": "Alert Routing Rule 1",
"alerts_source_id": "e637effb-df8f-45a5-8a3b-a4c555e85a61",
"condition_type": "all",
"enabled": false,
"position": 1,
"destination": null,
"created_at": "2025-08-07T22:33:27.751-07:00",
"updated_at": "2025-08-07T22:33:35.227-07:00",
"destinations": [],
"conditions": []
},
"relationships": {
"owning_teams": {
"data": [
{
"id": "ea5650a9-715e-4791-b22a-6bb36939afaf",
"type": "groups"
}
]
}
}
}
}