Alert responsibility settings

Create, read, update and delete alert responsibilities from the settings area.

Alert responsibility settings manage who is responsible for alerts, from the settings area. They are the same records the Alert responsibilities area serves. A create, update or delete needs the MANAGE_ALERT_RESPONSIBILITY permission, and without it returns 403. This area has 5 endpoints, and all seven SDKs call every one.

At a glance

Endpoint	Method	Path	What it does
List alert responsibilities (settings path)	GET	/settings/alert_responsibilities	Lists the alert responsibilities from the settings area, one page at a time.
Create an alert responsibility (settings path)	POST	/settings/alert_responsibilities	Creates an alert responsibility from the settings area.
Retrieve an alert responsibility (settings path)	GET	/settings/alert_responsibilities/{alert_responsibility_id}	Retrieves one alert responsibility from the settings area by its ar_ id.
Delete an alert responsibility (settings path)	DELETE	/settings/alert_responsibilities/{alert_responsibility_id}	Deletes an alert responsibility from the settings area. Nothing comes back.
Update an alert responsibility (settings path)	PATCH	/settings/alert_responsibilities/{alert_responsibility_id}	Changes an alert responsibility’s fields or its status from the settings area.

Before you call

Register your API credentials once when your app starts, as shown in Authentication. Every SDK sample on these pages then gets its client in one line. With cURL, send the access token in an Authorization header: Authorization: Bearer $ACCESS_TOKEN.

Things to know

• These are the same records as the Alert responsibilities area. /settings/alert_responsibilities and /alert_responsibility serve the same alert responsibilities.
• Writes need the MANAGE_ALERT_RESPONSIBILITY permission. Without it, a create, update or delete returns 403.
• Alert responsibility ids start with ar_. One record comes back under alert_responsibility, and name is required to create one.
• Listings page by cursor. Records sit under data; pass pagination.next_cursor as cursor to read the next page, and stop when pagination.has_more is false.