# 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.
: Modifying an existing recipient will change the destination of all triggers/burn alerts that use that recipient.


Endpoint: PUT /1/recipients/{recipientId}
Version: 1.0.0
Security: configuration_key

## Path parameters:

  - `recipientId` (string, required)
    Unique identifier (ID) of a Recipient.

## Response 401 fields (application/json):

  - `error` (string)

## Response 404 fields (application/json):

  - `error` (string)

## Response 409 fields (application/json):

  - `error` (string)

## Response 422 fields (application/problem+json):

  - `error` (string, required)

  - `status` (number, required)
    The HTTP status code of the error.

  - `type` (string, required)
    Type is a URI used to uniquely identify the type of error.

  - `title` (string, required)
    Title is a human-readable summary that explains the  of the problem.

  - `detail` (string)
    The general, human-readable error message.

  - `instance` (string)
    The unique identifier (ID) for this specific error.

  - `type_detail` (array)

  - `type_detail.field` (string)

  - `type_detail.code` (string)
    Enum: "invalid", "missing", "incorrect_type", "already_exists"

  - `type_detail.description` (string)