status_updates_subscribers
Creates, updates, deletes, gets or lists a status_updates_subscribers
resource.
Overview
Name | status_updates_subscribers |
Type | Resource |
Id | pagerduty.incidents.status_updates_subscribers |
Fields
The following fields are returned by SELECT
queries:
- get_incident_notification_subscribers
Name | Datatype | Description |
---|---|---|
subscriber_id | string | The ID of the entity being subscribed |
has_indirect_subscription | boolean | If this subcriber has an indirect subscription to this incident via another object |
subscribed_via | array | |
subscriber_type | string | The type of the entity being subscribed |
Methods
The following methods are available for this resource:
Name | Accessible by | Required Params | Optional Params | Description |
---|---|---|---|---|
get_incident_notification_subscribers | select | id | Accept | Retrieve a list of Notification Subscribers on the Incident. <!-- theme: warning --> > Users must be added through POST /incident/{id}/status_updates/subscribers to be returned from this endpoint.Scoped OAuth requires: subscribers.read |
create_incident_notification_subscribers | insert | id , data__subscribers | Accept | Subscribe the given entities to Incident Status Update Notifications. Scoped OAuth requires: subscribers.write |
_get_incident_notification_subscribers | exec | id | Accept | Retrieve a list of Notification Subscribers on the Incident. <!-- theme: warning --> > Users must be added through POST /incident/{id}/status_updates/subscribers to be returned from this endpoint.Scoped OAuth requires: subscribers.read |
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.
Name | Datatype | Description |
---|---|---|
id | string | The ID of the resource. |
Accept | string | The Accept header is used as a versioning header. |
SELECT
examples
- get_incident_notification_subscribers
Retrieve a list of Notification Subscribers on the Incident.
<!-- theme: warning -->
> Users must be added through POST /incident/{id}/status_updates/subscribers
to be returned from this endpoint.
Scoped OAuth requires: subscribers.read
SELECT
subscriber_id,
has_indirect_subscription,
subscribed_via,
subscriber_type
FROM pagerduty.incidents.status_updates_subscribers
WHERE id = '{{ id }}' -- required
AND Accept = '{{ Accept }}'
;
INSERT
examples
- create_incident_notification_subscribers
- Manifest
Subscribe the given entities to Incident Status Update Notifications.
Scoped OAuth requires: subscribers.write
INSERT INTO pagerduty.incidents.status_updates_subscribers (
data__subscribers,
id,
Accept
)
SELECT
'{{ subscribers }}' /* required */,
'{{ id }}',
'{{ Accept }}'
RETURNING
subscriptions
;
# Description fields are for documentation purposes
- name: status_updates_subscribers
props:
- name: id
value: string
description: Required parameter for the status_updates_subscribers resource.
- name: subscribers
value: array
- name: Accept
value: string
description: The `Accept` header is used as a versioning header.
Lifecycle Methods
- _get_incident_notification_subscribers
Retrieve a list of Notification Subscribers on the Incident.
<!-- theme: warning -->
> Users must be added through POST /incident/{id}/status_updates/subscribers
to be returned from this endpoint.
Scoped OAuth requires: subscribers.read
EXEC pagerduty.incidents.status_updates_subscribers._get_incident_notification_subscribers
@id='{{ id }}' --required,
@Accept='{{ Accept }}'
;