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": "18bf4e9c-5795-470d-ad2b-4942aa2b6c0e",
"type": "alert_routing_rules",
"attributes": {
"name": "Alert Routing Rule 1",
"alerts_source_id": "2ea415db-cc9a-4309-8823-c4e772e9f173",
"condition_type": "all",
"enabled": false,
"position": 1,
"created_at": "2025-07-18T16:31:21.958-07:00",
"updated_at": "2025-07-18T16:31:26.682-07:00",
"destinations": [],
"conditions": []
},
"relationships": {
"owning_teams": {
"data": [
{
"id": "b3d3b9a2-e3c1-41f4-a783-1ca15b654b8d",
"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": "18bf4e9c-5795-470d-ad2b-4942aa2b6c0e",
"type": "alert_routing_rules",
"attributes": {
"name": "Alert Routing Rule 1",
"alerts_source_id": "2ea415db-cc9a-4309-8823-c4e772e9f173",
"condition_type": "all",
"enabled": false,
"position": 1,
"created_at": "2025-07-18T16:31:21.958-07:00",
"updated_at": "2025-07-18T16:31:26.682-07:00",
"destinations": [],
"conditions": []
},
"relationships": {
"owning_teams": {
"data": [
{
"id": "b3d3b9a2-e3c1-41f4-a783-1ca15b654b8d",
"type": "groups"
}
]
}
}
}
}