# Endpoint to update the properties of the subscription.

# Update Subscription
---

The request body must contain the complete information about the subscription.

The following values can be updated: The __URL__ used for the webhook, the __event type__ applied to this URL and the __secret__, which is used to sign the payload.
It is not possible to change the identification of the subscription.

Omitting properties from the request body (e.g. secret) will result in a validation error and return the status code 400.

Endpoint: PUT /webhook/management/v1/{id}
Version: 1.0.0
Security: JSON Web Token

## Path parameters:

  - `id` (string, required)
    Subscription ID received when creating a subscription.
    Example: "d8znR1k1_0Kw305BsoPT"

## Header parameters:

  - `Authorization` (string, required)
    For each request, a valid access token must be provided in the Authorization header. See                       Authentication API for obtaining a valid token.

## Request fields (application/json):

  - `url` (string, required)
    HTTP URL to execute the webhook call with the POST method.
    Example: "https://api.merchant.com/event"

  - `event_type` (string, required)
    Type of the event to process by calling the API endpoint.
    Example: "INVOICE_INVOICE"

  - `secret` (string, required)
    Parameter given by the client to sign their payloads. Recommended to be unique for each URL.
    Example: "6GHbLH4d1Nx3eIs5CyLHCW4HuFi1qttpNSDawHKHlW7kurTpaddarwEKDWUI59IU"

## Response 200 fields (application/json):

  - `id` (string)
    ID of the subscription.
    Example: "d8znR1k1_0Kw305BsoPT"

  - `url` (string)
    HTTP URL to execute the webhook call with the POST method.
    Example: "https://api.merchant.com/event"

  - `event_type` (string)
    Type of the event to process by calling the API endpoint.
    Example: "INVOICE_INVOICE"

  - `secret` (string)
    Parameter given by the client to sign their payloads. Recommended to be unique for each URL.
    Example: "6GHbLH4d1Nx3eIs5CyLHCW4HuFi1qttpNSDawHKHlW7kurTpaddarwEKDWUI59IU"

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

  - `name` (string)
    Example: "ValidationError"

  - `message` (string)
    A message containing the error.
    Example: "Error while validating the JWT token."

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

  - `name` (string)
    Example: "UnauthorizedError"

  - `message` (string)
    A message containing the error.
    Example: "Bad request because the client could not be authorized."

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

  - `name` (string)
    Example: "ForbiddenError"

  - `message` (string)
    A message containing the error.
    Example: "Bad request because the client is not allowed to update the resource."

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

  - `name` (string)
    Example: "NotFoundError"

  - `message` (string)
    A message containing the error.
    Example: "Bad request because the resource cannot be found."

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

  - `message` (string)
    A message containing the error.
    Example: "Bad request because the HTTP method is not allowed."

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

  - `message` (string)
    A message containing the error.
    Example: "Bad request because the server cannot produce a response matching the list of acceptable values."

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

  - `message` (string)
    A message containing the error.
    Example: "Bad request because the payload format is not supported."

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

  - `message` (string)
    A message containing the error.
    Example: "Invalid authorization token."