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/escalation_chains/
|
2024-06-17 11:31:35 -04:00
|
|
|
title: Escalation chains 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
|
|
|
# Escalation chains HTTP API
|
|
|
|
|
|
|
|
|
|
## Create an escalation chain
|
2022-06-03 08:09:47 -06:00
|
|
|
|
2024-12-11 08:54:00 -03:00
|
|
|
**Required permission**: `grafana-oncall-app.escalation-chains:write`
|
|
|
|
|
|
2022-06-03 08:09:47 -06:00
|
|
|
```shell
|
|
|
|
|
curl "{{API_URL}}/api/v1/escalation_chains/" \
|
|
|
|
|
--request POST \
|
|
|
|
|
--header "Authorization: meowmeowmeow" \
|
|
|
|
|
--header "Content-Type: application/json" \
|
|
|
|
|
--data '{
|
|
|
|
|
"name": "example-chain"
|
|
|
|
|
}'
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
The above command returns JSON structured in the following way:
|
|
|
|
|
|
|
|
|
|
```json
|
|
|
|
|
{
|
2022-06-09 10:08:07 +01:00
|
|
|
"id": "FWDL7M6N6I9HE",
|
|
|
|
|
"name": "example-chain",
|
|
|
|
|
"team_id": null
|
2022-06-03 08:09:47 -06:00
|
|
|
}
|
|
|
|
|
```
|
|
|
|
|
|
2022-06-09 10:08:07 +01:00
|
|
|
| Parameter | Required | Description |
|
|
|
|
|
| --------- | :------: | :--------------------------- |
|
|
|
|
|
| name | yes | Name of the escalation chain |
|
|
|
|
|
| team_id | no | ID of the team |
|
2022-06-03 08:09:47 -06:00
|
|
|
|
|
|
|
|
**HTTP request**
|
|
|
|
|
|
|
|
|
|
`POST {{API_URL}}/api/v1/escalation_chains/`
|
|
|
|
|
|
2024-06-17 11:31:35 -04:00
|
|
|
## Get an escalation chain
|
2022-06-03 08:09:47 -06:00
|
|
|
|
2024-12-11 08:54:00 -03:00
|
|
|
**Required permission**: `grafana-oncall-app.escalation-chains:read`
|
|
|
|
|
|
2022-06-03 08:09:47 -06:00
|
|
|
```shell
|
|
|
|
|
curl "{{API_URL}}/api/v1/escalation_chains/F5JU6KJET33FE/" \
|
|
|
|
|
--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": "F5JU6KJET33FE",
|
|
|
|
|
"name": "default",
|
|
|
|
|
"team_id": null
|
2022-06-03 08:09:47 -06:00
|
|
|
}
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
**HTTP request**
|
|
|
|
|
|
|
|
|
|
`GET {{API_URL}}/api/v1/escalation_chains/<ESCALATION_CHAIN_ID>/`
|
|
|
|
|
|
2024-06-17 11:31:35 -04:00
|
|
|
## List escalation chains
|
2022-06-03 08:09:47 -06:00
|
|
|
|
2024-12-11 08:54:00 -03:00
|
|
|
**Required permission**: `grafana-oncall-app.escalation-chains:read`
|
|
|
|
|
|
2022-06-03 08:09:47 -06:00
|
|
|
```shell
|
|
|
|
|
curl "{{API_URL}}/api/v1/escalation_chains/" \
|
|
|
|
|
--request GET \
|
|
|
|
|
--header "Authorization: meowmeowmeow" \
|
2022-06-09 10:08:07 +01:00
|
|
|
--header "Content-Type: application/json"
|
2022-06-03 08:09:47 -06:00
|
|
|
```
|
|
|
|
|
|
|
|
|
|
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": "F5JU6KJET33FE",
|
|
|
|
|
"name": "default",
|
|
|
|
|
"team_id": null
|
|
|
|
|
}
|
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": 50,
|
|
|
|
|
"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
|
|
|
**HTTP request**
|
|
|
|
|
|
|
|
|
|
`GET {{API_URL}}/api/v1/escalation_chains/`
|
|
|
|
|
|
2024-06-17 11:31:35 -04:00
|
|
|
## Delete an escalation chain
|
2022-06-03 08:09:47 -06:00
|
|
|
|
2024-12-11 08:54:00 -03:00
|
|
|
**Required permission**: `grafana-oncall-app.escalation-chains:write`
|
|
|
|
|
|
2022-06-03 08:09:47 -06:00
|
|
|
```shell
|
|
|
|
|
curl "{{API_URL}}/api/v1/escalation_chains/F5JU6KJET33FE/" \
|
|
|
|
|
--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/escalation_chains/<ESCALATION_CHAIN_ID>/`
|