> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-6.2/voyage-management-system/step-by-step-guides/webhook-subscriptions/create-webhook-subscription.md).

# Create Webhook Subscription

1. Open the **Webhooks** module in the Setup section.
2. Click **Create Webhook Subscription**<img src="/files/-M23aB95JDSUt7kYOdWo" alt="" data-size="line">in the top right corner.
3. Fill in all required fields listed below in the Create New Subscription window.
4. Click **Create**.

### **Required fields**

| **Field**      | Description                                                  |
| -------------- | ------------------------------------------------------------ |
| *User*         | User to receive the notifications                            |
| *Object Type*  | Name of the subscribed Dataloy object                        |
| *Event Type*   | Type of event to *Object*                                    |
| *Alert Script* | Subscribe to events based on the result of a DLPAlertScript. |
| *Channel Type* | Channel used to send notification                            |
| *Url*          | Endpoint to receive the subscription                         |

{% hint style="info" %}
**Field Conditions**

A webhook subscription can only have an *Object Type* and an *Event Type* or an *Alert Script*. The corresponding fields are disabled to match this condition.

If the *Channel Type* chosen is HTTP, then the *URL* field must also be filled in.&#x20;
{% endhint %}

![Create Webhook Subscription Dialog](/files/-MUwQ8NnqRh9_OJiLItD)

When choosing **HTTP** as Channel Type, you can also choose whether to add the *Password*, *Access Token* or *Request Access Token* fields.

![Channel Type HTTP Options](/files/-MUwX7oszRo7wLvmrJIL)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.dataloy.com/release-6.2/voyage-management-system/step-by-step-guides/webhook-subscriptions/create-webhook-subscription.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
