Get a specific alert route by id. Note: This endpoint requires access to Advanced Alert Routing. If you’re unsure whether you have access to this feature, please contact Rootly customer support.
true, the response will include IDs for all nested resources (destinations, condition_groups, conditions). This is useful when you need to reference these nested resources for updates or deletions via PATCH requests.Example: GET /v1/alert_routes/{id}?show_nested_ids=true
curl --request GET \
--url https://api.rootly.com/v1/alert_routes/{id} \
--header 'Authorization: Bearer <token>'{
"data": {
"id": "958596d5-c62d-42c1-871f-4980387ba484",
"type": "alert_routes",
"attributes": {
"name": "Test Alert Route-b47e",
"enabled": true,
"created_at": "2026-02-13T18:03:38.191-08:00",
"updated_at": "2026-02-13T18:03:38.191-08:00",
"alerts_source_ids": [],
"owning_team_ids": [],
"rules": []
}
}
}Was this page helpful?
curl --request GET \
--url https://api.rootly.com/v1/alert_routes/{id} \
--header 'Authorization: Bearer <token>'{
"data": {
"id": "958596d5-c62d-42c1-871f-4980387ba484",
"type": "alert_routes",
"attributes": {
"name": "Test Alert Route-b47e",
"enabled": true,
"created_at": "2026-02-13T18:03:38.191-08:00",
"updated_at": "2026-02-13T18:03:38.191-08:00",
"alerts_source_ids": [],
"owning_team_ids": [],
"rules": []
}
}
}