Skip to main content

oncall_handoff_notification_rules

Creates, updates, deletes, gets or lists an oncall_handoff_notification_rules resource.

Overview

Nameoncall_handoff_notification_rules
TypeResource
Idpagerduty.users.oncall_handoff_notification_rules

Fields

The following fields are returned by SELECT queries:

The user's handoff notification rule requested.

NameDatatypeDescription
idstring
contact_methodobject
handoff_typestringThe type of handoff being created. (default: both)
notify_advance_in_minutesintegerThe delay before firing the rule, in minutes.

Methods

The following methods are available for this resource:

NameAccessible byRequired ParamsOptional ParamsDescription
get_user_handoff_notifiaction_ruleselectid, oncall_handoff_notification_rule_idAccept, Content-TypeGet details about a User's Handoff Notification Rule.
Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account.
For more information see the API Concepts Document

Scoped OAuth requires: users.read
get_user_handoff_notification_rulesselectidAccept, Content-TypeList Handoff Notification Rules of your PagerDuty User.
Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account.
For more information see the API Concepts Document

Scoped OAuth requires: users.read
create_user_handoff_notification_ruleinsertid, data__oncall_handoff_notification_ruleAccept, Content-TypeCreate a new Handoff Notification Rule.
Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account.
For more information see the API Concepts Document

Scoped OAuth requires: users.write
delete_user_handoff_notification_ruledeleteid, oncall_handoff_notification_rule_idAccept, Content-TypeRemove a User's Handoff Notification Rule.
Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account.
For more information see the API Concepts Document

Scoped OAuth requires: users.write
_get_user_handoff_notification_rulesexecidAccept, Content-TypeList Handoff Notification Rules of your PagerDuty User.
Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account.
For more information see the API Concepts Document

Scoped OAuth requires: users.read
_get_user_handoff_notifiaction_ruleexecid, oncall_handoff_notification_rule_idAccept, Content-TypeGet details about a User's Handoff Notification Rule.
Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account.
For more information see the API Concepts Document

Scoped OAuth requires: users.read
update_user_handoff_notificationexecid, oncall_handoff_notification_rule_id, oncall_handoff_notification_ruleAccept, Content-TypeUpdate a User's Handoff Notification Rule.
Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account.
For more information see the API Concepts Document

Scoped OAuth requires: users.write

Parameters

Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.

NameDatatypeDescription
idstringThe ID of the resource.
oncall_handoff_notification_rule_idstringThe oncall handoff notification rule ID on the user.
AcceptstringThe Accept header is used as a versioning header.
Content-Typestring

SELECT examples

Get details about a User's Handoff Notification Rule.
Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account.
For more information see the API Concepts Document

Scoped OAuth requires: users.read

SELECT
id,
contact_method,
handoff_type,
notify_advance_in_minutes
FROM pagerduty.users.oncall_handoff_notification_rules
WHERE id = '{{ id }}' -- required
AND oncall_handoff_notification_rule_id = '{{ oncall_handoff_notification_rule_id }}' -- required
AND Accept = '{{ Accept }}'
AND Content-Type = '{{ Content-Type }}'
;

INSERT examples

Create a new Handoff Notification Rule.
Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account.
For more information see the API Concepts Document

Scoped OAuth requires: users.write

INSERT INTO pagerduty.users.oncall_handoff_notification_rules (
data__oncall_handoff_notification_rule,
id,
Accept,
Content-Type
)
SELECT
'{{ oncall_handoff_notification_rule }}' /* required */,
'{{ id }}',
'{{ Accept }}',
'{{ Content-Type }}'
RETURNING
oncall_handoff_notification_rule
;

DELETE examples

Remove a User's Handoff Notification Rule.
Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account.
For more information see the API Concepts Document

Scoped OAuth requires: users.write

DELETE FROM pagerduty.users.oncall_handoff_notification_rules
WHERE id = '{{ id }}' --required
AND oncall_handoff_notification_rule_id = '{{ oncall_handoff_notification_rule_id }}' --required
AND Accept = '{{ Accept }}'
AND Content-Type = '{{ Content-Type }}'
;

Lifecycle Methods

List Handoff Notification Rules of your PagerDuty User.
Users are members of a PagerDuty account that have the ability to interact with Incidents and other data on the account.
For more information see the API Concepts Document

Scoped OAuth requires: users.read

EXEC pagerduty.users.oncall_handoff_notification_rules._get_user_handoff_notification_rules 
@id='{{ id }}' --required,
@Accept='{{ Accept }}',
@Content-Type='{{ Content-Type }}'
;