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/personal_notification_rules/
2024-06-17 11:31:35 -04:00
title: Personal notification rules 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
# Personal notification rules HTTP API
## Post a personal notification rule
2022-06-03 08:09:47 -06:00
2024-12-11 08:54:00 -03:00
**Required permission**: `grafana-oncall-app.user-settings:write` (user authentication only)
2022-06-03 08:09:47 -06:00
```shell
curl "{{API_URL}}/api/v1/personal_notification_rules/" \
--request POST \
--header "Authorization: meowmeowmeow" \
--header "Content-Type: application/json" \
--data '{
"user_id": "U4DNY931HHJS5",
"type": "notify_by_sms"
}'
```
The above command returns JSON structured in the following way:
```json
{
2022-06-09 10:08:07 +01:00
"id": "NT79GA9I7E4DJ",
"user_id": "U4DNY931HHJS5",
"position": 0,
"important": false,
"type": "notify_by_sms"
2022-06-03 08:09:47 -06:00
}
```
2022-06-09 10:08:07 +01:00
| Parameter | Required | Description |
| ----------- | :------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `user_id` | Yes | User ID |
| `position` | Optional | Personal notification rules execute one after another starting from `position=0` . `Position=-1` will put the escalation policy to the end of the list. A new escalation policy created with a position of an existing escalation policy will move the old one (and all following) down on the list. |
2025-02-18 14:53:07 -03:00
| `type` | Yes | One of: `wait` , `notify_by_slack` , `notify_by_sms` , `notify_by_phone_call` , `notify_by_telegram` , `notify_by_email` , `notify_by_mobile_app` , `notify_by_mobile_app_critical` , `notify_by_webhook` or `notify_by_msteams` (**NOTE** `notify_by_msteams` is only available on Grafana Cloud). |
2024-07-05 15:08:17 -04:00
| `duration` | Optional | A time in seconds to wait (when `type=wait` ). Can be one of 60, 300, 900, 1800, or 3600. |
2022-06-09 10:08:07 +01:00
| `important` | Optional | Boolean value indicates if a rule is "important". Default is `false` . |
2022-06-03 08:09:47 -06:00
**HTTP request**
`POST {{API_URL}}/api/v1/personal_notification_rules/`
2024-06-17 11:31:35 -04:00
## Get personal notification rule
2022-06-03 08:09:47 -06:00
2024-12-11 08:54:00 -03:00
**Required permission**: `grafana-oncall-app.user-settings:read` (user authentication only)
2022-06-03 08:09:47 -06:00
```shell
curl "{{API_URL}}/api/v1/personal_notification_rules/ND9EHN5LN1DUU/" \
--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
"id": "ND9EHN5LN1DUU",
"user_id": "U4DNY931HHJS5",
"position": 1,
"duration": 300,
"important": false,
"type": "wait"
2022-06-03 08:09:47 -06:00
}
```
**HTTP request**
`GET {{API_URL}}/api/v1/personal_notification_rules/<PERSONAL_NOTIFICATION_RULE_ID>/`
2024-06-17 11:31:35 -04:00
## List personal notification rules
2022-06-03 08:09:47 -06:00
2024-12-11 08:54:00 -03:00
**Required permission**: `grafana-oncall-app.user-settings:read` (user authentication only)
2022-06-03 08:09:47 -06:00
```shell
curl "{{API_URL}}/api/v1/personal_notification_rules/" \
--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 ways:
```json
{
2022-06-09 10:08:07 +01:00
"count": 4,
"next": null,
"previous": null,
"results": [
{
"id": "NT79GA9I7E4DJ",
"user_id": "U4DNY931HHJS5",
"position": 0,
"important": false,
"type": "notify_by_sms"
},
{
"id": "ND9EHN5LN1DUU",
"user_id": "U4DNY931HHJS5",
"position": 1,
"duration": 300,
"important": false,
"type": "wait"
},
{
"id": "NEF49YQ1HNPDD",
"user_id": "U4DNY931HHJS5",
"position": 2,
"important": false,
"type": "notify_by_phone_call"
},
{
"id": "NWAL6WFJNWDD8",
"user_id": "U4DNY931HHJS5",
"position": 0,
"important": true,
"type": "notify_by_phone_call"
}
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
The following available filter parameters should be provided as `GET` arguments:
2022-06-09 10:08:07 +01:00
- `user_id`
- `important`
2022-06-03 08:09:47 -06:00
**HTTP Request**
`GET {{API_URL}}/api/v1/personal_notification_rules/`
2024-06-17 11:31:35 -04:00
## Delete a personal notification rule
2022-06-03 08:09:47 -06:00
2024-12-11 08:54:00 -03:00
**Required permission**: `grafana-oncall-app.user-settings:write` (user authentication only)
2022-06-03 08:09:47 -06:00
```shell
curl "{{API_URL}}/api/v1/personal_notification_rules/NWAL6WFJNWDD8/" \
--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/personal_notification_rules/<PERSONAL_NOTIFICATION_RULE_ID>/`