notification_rules
Overview
| Name | notification_rules |
| Type | Resource |
| Id | pagerduty.users.notification_rules |
Fields
| Name | Datatype | Description |
|---|---|---|
id | string | |
_type | string | The type of object being created. |
contact_method | object | |
html_url | string | a URL at which the entity is uniquely displayed in the Web app |
self | string | the API show URL at which the object is accessible |
start_delay_in_minutes | integer | The delay before firing the rule, in minutes. |
summary | string | A short-form, server-generated string that provides succinct, important information about an object suitable for primary labeling of an entity in a client. In many cases, this will be identical to name, though it is not intended to be an identifier. |
type | string | A string that determines the schema of the object. This must be the standard name for the entity, suffixed by _reference if the object is a reference. |
urgency | string | Which incident urgency this rule is used for. Account must have the urgencies ability to have a low urgency notification rule. |
Methods
| Name | Accessible by | Required Params | Description |
|---|---|---|---|
get_user_notification_rule | SELECT | id, notification_rule_id | Get details about a user's 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:contact_methods.read |
get_user_notification_rules | SELECT | id | List 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:contact_methods.read |
create_user_notification_rule | INSERT | id, data__notification_rule | Create a new 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:contact_methods.write |
delete_user_notification_rule | DELETE | id, notification_rule_id | Remove a user's 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:contact_methods.write |
_get_user_notification_rule | EXEC | id, notification_rule_id | Get details about a user's 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:contact_methods.read |
_get_user_notification_rules | EXEC | id | List 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:contact_methods.read |
update_user_notification_rule | EXEC | id, notification_rule_id, data__notification_rule | Update a user's 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:contact_methods.write |