# Update an existing webhook subscription

After creation, subscriptions can be updated to change what events are subscribed to, what url to send the payloads to, and other settings such as whether the subscription is active. Any values that can be set on the subscription when creating it can be updated.  The update method is a patch operation, so only properties you send in the request will be updated on the record. The events property, however, does not support partial updates as an array.   The access token used when updating a subscription must have the webhooks.write auth scope. 


Endpoint: PUT /v2/webhooks/subscriptions/{subscription_id}
Version: v2
Security: oauth2_as_a_user, oauth2_as_a_server

## Path parameters:

  - `subscription_id` (string, required)
    Id of the subscription to update

## Request fields (application/json):

  - `url` (string)
    The url that will be called when delivering events for this subscription.
    Example: "https://example.com/webhook"

  - `authorization_header` (string)
    A value will be sent in every delivery as the 'Authorization' header value in the POST request.
    Example: "Bearer abc123-some-token"

  - `active` (boolean)
    Whether the subscription is "turned on". Inactive subscriptions will not send deliveries to the subscription url except for ping deliveries.
    Example: true

  - `events` (array)

  - `events.name` (any)
    The name of the event.
    Example: "content_published"

  - `events.version` (any)
    The version of the event this subscription uses.
    Example: "1"

## Response 200 fields (application/json):

  - `data` (object, required)

  - `data.id` (string)
    Unique identifier for this subscription.
    Example: "abc123"

  - `data.url` (string)
    The url that will be called when delivering events for this subscription.
    Example: "https://example.com/webhook"

  - `data.authorization_header` (string)
    A value will be sent in every delivery as the 'Authorization' header value in the POST request.
    Example: "Bearer abc123-some-token"

  - `data.active` (boolean)
    Whether the subscription is "turned on". Inactive subscriptions will not send deliveries to the subscription url except for ping deliveries.
    Example: true

  - `data.events` (array)

  - `data.events.name` (any)
    The name of the event.
    Example: "content_published"

  - `data.events.version` (any)
    The version of the event this subscription uses.
    Example: "1"

  - `data.created_at` (string)
    Example: "2000-01-01T00:00:00Z"

  - `data.updated_at` (string)
    Example: "2000-01-01T00:00:00Z"