2022-06-09 10:08:07 +01:00
---
2022-10-26 12:32:47 -04:00
canonical: https://grafana.com/docs/oncall/latest/oncall-api-reference/routes/
2022-06-09 10:08:07 +01:00
title: Routes HTTP API
2024-08-15 15:29:56 -04:00
weight: 0
2024-08-09 15:24:24 +01:00
refs:
pagination:
- pattern: /docs/oncall/
destination: /docs/oncall/< ONCALL_VERSION > /oncall-api-reference/#pagination
- pattern: /docs/grafana-cloud/
destination: /docs/grafana-cloud/alerting-and-irm/oncall/oncall-api-reference/#pagination
2022-06-09 10:08:07 +01:00
---
2022-06-03 08:09:47 -06:00
2024-06-17 11:31:35 -04:00
# Routes HTTP API
## Create a route
2022-06-03 08:09:47 -06:00
2024-12-11 08:54:00 -03:00
**Required permission**: `grafana-oncall-app.integrations:write`
2022-06-03 08:09:47 -06:00
```shell
curl "{{API_URL}}/api/v1/routes/" \
--request POST \
--header "Authorization: meowmeowmeow" \
--header "Content-Type: application/json" \
--data '{
"integration_id": "CFRPV98RPR1U8",
"escalation_chain_id": "F5JU6KJET33FE",
"routing_regex": "us-(east|west)",
"position": 0,
"slack": {
"channel_id": "CH23212D"
}
}'
```
The above command returns JSON structured in the following way:
```json
{
2022-06-09 10:08:07 +01:00
"id": "RIYGUJXCPFHXY",
"integration_id": "CFRPV98RPR1U8",
"escalation_chain_id": "F5JU6KJET33FE",
"routing_regex": "us-(east|west)",
"position": 0,
"is_the_last_route": false,
"slack": {
"channel_id": "CH23212D"
}
2022-06-03 08:09:47 -06:00
}
```
Routes allow you to direct different alerts to different messenger channels and escalation chains. Useful for:
2022-06-09 10:08:07 +01:00
- Important/non-important alerts
- Alerts for different engineering groups
- Snoozing spam & debugging alerts
2022-06-03 08:09:47 -06:00
2022-06-09 10:08:07 +01:00
| Parameter | Unique | Required | Description |
2023-06-09 08:57:19 +02:00
| --------------------- | :----: | :------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
2022-06-09 10:08:07 +01:00
| `integration_id` | No | Yes | Each route is assigned to a specific integration. |
2023-03-16 09:40:50 +00:00
| `escalation_chain_id` | No | Yes | Each route is assigned a specific escalation chain. Explicitly pass `null` to create a route without an escalation chain assigned. |
2023-03-08 16:42:18 +08:00
| `routing_type` | Yes | No | Routing type that can be either `jinja2` or `regex` (default value) |
| `routing_regex` | Yes | Yes | Jinja2 template or Python Regex query (use < https: // regex101 . com /> for debugging). OnCall chooses the route for an alert in case there is a match inside the whole alert payload. |
2022-06-09 10:08:07 +01:00
| `position` | Yes | Optional | Route matching is performed one after another starting from position=`0` . Position=`-1` will put the route to the end of the list before `is_the_last_route` . A new route created with a position of an existing route will move the old route (and all following routes) down in the list. |
| `slack` | Yes | Optional | Dictionary with Slack-specific settings for a route. |
2022-06-03 08:09:47 -06:00
**HTTP request**
`POST {{API_URL}}/api/v1/routes/`
2024-06-17 11:31:35 -04:00
## Get a route
2022-06-03 08:09:47 -06:00
2024-12-11 08:54:00 -03:00
**Required permission**: `grafana-oncall-app.integrations:read`
2022-06-03 08:09:47 -06:00
```shell
curl "{{API_URL}}/api/v1/routes/RIYGUJXCPFHXY/" \
--request GET \
--header "Authorization: meowmeowmeow" \
--header "Content-Type: application/json" \
```
The above command returns JSON structured in the following way:
```json
{
2022-06-09 10:08:07 +01:00
"id": "RIYGUJXCPFHXY",
"integration_id": "CFRPV98RPR1U8",
"escalation_chain_id": "F5JU6KJET33FE",
"routing_regex": "us-(east|west)",
"position": 0,
"is_the_last_route": false,
"slack": {
"channel_id": "CH23212D"
}
2022-06-03 08:09:47 -06:00
}
```
**HTTP request**
`GET {{API_URL}}/api/v1/routes/<ROUTE_ID>/`
2024-06-17 11:31:35 -04:00
## List routes
2022-06-03 08:09:47 -06:00
2024-12-11 08:54:00 -03:00
**Required permission**: `grafana-oncall-app.integrations:read`
2022-06-03 08:09:47 -06:00
```shell
curl "{{API_URL}}/api/v1/routes/" \
--request GET \
--header "Authorization: meowmeowmeow" \
--header "Content-Type: application/json"
```
The above command returns JSON structured in the following way:
```json
{
2022-06-09 10:08:07 +01:00
"count": 2,
"next": null,
"previous": null,
"results": [
{
"id": "RIYGUJXCPFHXY",
"integration_id": "CFRPV98RPR1U8",
"escalation_chain_id": "F5JU6KJET33FE",
"routing_regex": "us-(east|west)",
"position": 0,
"is_the_last_route": false,
"slack": {
"channel_id": "CH23212D"
}
},
{
"id": "RVBE4RKQSCGJ2",
"integration_id": "CFRPV98RPR1U8",
"escalation_chain_id": "F5JU6KJET33FE",
"routing_regex": ".*",
"position": 1,
"is_the_last_route": true,
"slack": {
"channel_id": "CH23212D"
}
}
augment API response pagination attributes (#2471)
# What this PR does
This PR:
- adds a few attributes to paginated API responses
- removes channel filter "send demo alert" internal API endpoint + tests
(this endpoint was marked as deprecated + not consumed by the web UI)
With the new paginated API response schema, the web UI will no longer
need to:
- hardcode `ITEMS_PER_PAGE` for each table
- manually calculate total number of pages
(these two things ☝️ will be done in
https://github.com/grafana/oncall/issues/2476)
For `GET /api/internal/v1/alertgroups` the response will now look like
this:
```diff
{
"next": <url> | None,
"previous": <url> | None,
"results": [],
++ "page_size": <int>
}
```
For all other paginated API responses, the response will now look like:
```diff
{
"count": <int>,
"next": <url> | None,
"previous": <url> | None,
"results": [],
++ "page_size": <int>,
++ "current_page_number": <int>,
++ "total_pages": <int>
}
```
## TODO
- [x] update public API docs to include these new attributes
## Checklist
- [x] Unit, integration, and e2e (if applicable) tests updated
- [x] Documentation added (or `pr:no public docs` PR label added if not
required)
- [x] `CHANGELOG.md` updated (or `pr:no changelog` PR label added if not
required)
2023-07-14 17:19:40 +02:00
],
"current_page_number": 1,
"page_size": 25,
"total_pages": 1
2022-06-03 08:09:47 -06:00
}
```
2024-08-09 15:24:24 +01:00
> **Note**: The response is [paginated](ref:pagination). You may need to make multiple requests to get all records.
2022-06-03 08:09:47 -06:00
The following available filter parameters should be provided as `GET` arguments:
2022-06-09 10:08:07 +01:00
- `integration_id`
- `routing_regex` (Exact match)
2022-06-03 08:09:47 -06:00
**HTTP request**
`GET {{API_URL}}/api/v1/routes/`
2024-06-17 11:31:35 -04:00
## Update route
2022-06-03 08:09:47 -06:00
2024-12-11 08:54:00 -03:00
**Required permission**: `grafana-oncall-app.integrations:write`
2022-06-03 08:09:47 -06:00
```shell
curl "{{API_URL}}/api/v1/routes/RIYGUJXCPFHXY/" \
--request PUT \
--header "Authorization: meowmeowmeow" \
--header "Content-Type: application/json" \
--data '{
"routing_regex": "us-(east|west)",
"position": 0,
"slack": {
"channel_id": "CH23212D"
}
}'
```
The above command returns JSON structured in the following way:
```json
{
2022-06-09 10:08:07 +01:00
"id": "RIYGUJXCPFHXY",
"integration_id": "CFRPV98RPR1U8",
"escalation_chain_id": "F5JU6KJET33FE",
"routing_regex": "us-(east|west)",
"position": 0,
"is_the_last_route": false,
"slack": {
"channel_id": "CH23212D"
}
2022-06-03 08:09:47 -06:00
}
```
**HTTP request**
`PUT {{API_URL}}/api/v1/routes/<ROUTE_ID>/`
2024-06-17 11:31:35 -04:00
## Delete a route
2022-06-03 08:09:47 -06:00
2024-12-11 08:54:00 -03:00
**Required permission**: `grafana-oncall-app.integrations:write`
2022-06-03 08:09:47 -06:00
```shell
curl "{{API_URL}}/api/v1/routes/RIYGUJXCPFHXY/" \
--request DELETE \
--header "Authorization: meowmeowmeow" \
--header "Content-Type: application/json"
```
**HTTP request**
2022-06-09 10:08:07 +01:00
`DELETE {{API_URL}}/api/v1/routes/<ROUTE_ID>/`