# Renew a webhook subscription

Renews an existing webhook subscription to extend its expiration date.

Features:
- Extends subscription expiration by 1 month from current expiration date.
- Subscriptions can only be renewed 5 days before expiration.

Example Use Case: An operations manager wants to continue receiving webhook notifications for an existing subscription. Using this endpoint, they can extend the subscription without recreating it.

For more information on setting up and managing webhooks, see the Event Notifications (Webhook) Guide.

Endpoint: POST /api/v2/webhooks/subscriptions/{subscriptionId}/renewals
Version: 2.4.0
Security: X-Api-Client-Id, X-Auth-Token

## Path parameters:

  - `subscriptionId` (string, required)
    The unique identifier of the webhook subscription to renew.
    Example: "webhook-sub-12345"

## Response 200 fields (application/json):

  - `id` (string)
    Unique identifier for the webhook subscription.
    Example: "webhook-sub-12345"

  - `event` (string)
    The event type that this subscription is listening for.
    Example: "FLIGHT_UPDATE"

  - `callbackUrl` (string)
    The URL where webhook notifications will be sent.
    Example: "https://example.com/webhooks"

  - `status` (string)
    Status of the webhook subscription indicating whether it is active and receiving notifications or inactive.
    Enum: "ACTIVE", "INACTIVE"

  - `createdAtDateTime` (string)
    The date and time when the webhook subscription was created.
    Example: "2024-01-15T10:30:00.000Z"

  - `updatedAtDateTime` (string)
    The date and time when the webhook subscription was last updated.
    Example: "2024-01-15T10:30:00.000Z"

  - `expirationDateTime` (string)
    The date and time when the webhook subscription will expire.
    Example: "2024-02-15T10:30:00.000Z"


## Response 400 fields

## Response 401 fields

## Response 403 fields

## Response 404 fields