# Recipients

Honeycomb Recipients allow you to define and manage the Recipients that will get notified by a Trigger or Burn Alert.

The types of Recipients supported are: PagerDuty, Email, Webhook, Microsoft Teams, and Slack.



## Create a Recipient

 - [POST /1/recipients](https://api-docs.honeycomb.io/api/recipients/createrecipient.md): Unlike many resources, Recipients are not linked to a specific Environment or Dataset. The Recipient will be created for the Team associated with your API key.
The  fields will vary depending on the  of Recipient. Use the drop-down to view the specific fields for each  value.
Before Slack Recipients can be created, the Slack OAuth flow in the Integration Center must be completed.


## List all Recipients

 - [GET /1/recipients](https://api-docs.honeycomb.io/api/recipients/listrecipients.md): Retrieve all recipients for a team.


## Get a single Recipient

 - [GET /1/recipients/{recipientId}](https://api-docs.honeycomb.io/api/recipients/getrecipient.md): Retrieve a Recipient by recipient ID.


## Update a Recipient

 - [PUT /1/recipients/{recipientId}](https://api-docs.honeycomb.io/api/recipients/updaterecipient.md): 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.
: Modifying an existing recipient will change the destination of all triggers/burn alerts that use that recipient.


## Delete a Recipient

 - [DELETE /1/recipients/{recipientId}](https://api-docs.honeycomb.io/api/recipients/deleterecipient.md): Delete a recipient by specifying the recipient ID.
A Recipient can only be deleted if it is NOT in use by any Triggers or Burn Alerts associated to the team.