Update a Recipient
Update a Recipient by specifying the recipient ID and full recipient details. (Partial PUT is not supported.) Updates to the Recipient Type is not supported. For example, changing an existing Recipient from PagerDuty to Email is not allowed. Important: Modifying an existing recipient will change the destination of all triggers/burn alerts that use that recipient.
Authorizations
Authenticate using a Honeycomb Configuration Key.
Pass the Token in the X-Honeycomb-Team header:
X-Honeycomb-Team: 1234567890123456789012If you created your key using the API, use data.attributes.secret; this is the same value as the Token in the UI.
To learn how to create a Configuration Key, visit Manage Environment API Keys. To learn more about authenticating requests, visit API Authentication.
Path Parameters
Unique identifier (ID) of a Recipient.
Body
Response
Success
- Option 1
- Option 2
- Option 3
- Option 4
- Option 5
- Option 6
One of the supported Recipient Types
pagerduty "yUheCUmgZ8p"
ISO8601 formatted time the Recipient was created.
"2022-07-26T22:38:04Z"
ISO8601 formatted time the Recipient was updated.
"2022-07-26T22:38:04Z"
Specific schema for the Pagerduty Recipient Type