# Create a new webhook subscription

Subscriptions are configurations that define what events you want to receive webhooks for. A url and at least one event are required for a subscription. If your server requires authorization, the authorization_header property allows you to specify what value to send in the "Authorization" http header of every delivery to your url.  More information about creating webhook subscriptions is available on the Creating Webhook Subscriptions page, and the list of available events is available on the Event List page.  The access token used when creating a subscription must have the webhooks.write auth scope. 


Endpoint: POST /v2/webhooks/subscriptions
Version: v2
Security: oauth2_as_a_user, oauth2_as_a_server

## 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 201 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"