> For the complete documentation index, see [llms.txt](https://cactus-1.gitbook.io/cactusdash-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cactus-1.gitbook.io/cactusdash-guide/webhooks.md).

# Webhooks

You can configure Webhooks in the Settings section:<br>

<figure><img src="/files/YJ7R2j54M8HJRUTlWsdl" alt=""><figcaption></figcaption></figure>

There are 2 types of them:

### 1. Discord URL

This type of webhooks is sent to the specified channel. They specify the following actions with licenses:\
— renewal\
— unbind\
— deletion<br>

<div align="left"><figure><img src="/files/GxYfo10yo85ZgYysXqga" alt="" width="375"><figcaption></figcaption></figure></div>

### 2. API URL

&#x20;:warning: This type is relevant if you use our API in your internal products (apps, extensions etc...)&#x20;

Specify the API URL of your product to receive messages about the following:

Events

1. Changing the license renewal date
2. Removing the license
3. Undind

The initiators of these events may be:

1. The system
2. The license holder (user)
3. Admin (owner)

In addition, full license information will be sent (license key, owner username, renewal date, etc)


---

# 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, and the optional `goal` query parameter:

```
GET https://cactus-1.gitbook.io/cactusdash-guide/webhooks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.