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

# Webhooks

**Webhook URL** is the endpoint on your side that receives a GET or POST request from TADS when a user triggers an event. Optionally, you can add it when [creating a widget.](/docs/getting-started/publishers/create-widget.md)

<div align="left"><figure><img src="/files/FUqnO1YQNpeqDIDpzLGN" alt=""><figcaption></figcaption></figure></div>

The type of event that triggers the webhook is automatically defined by the widget format:

* For **TGB format**, the webhook is triggered **on ad click**.
* For **Fullscreen format**, the webhook is triggered **on ad view**.

Each POST request includes json object with the following data:

* **`telegram_id`** (string) – user Telegram  ID
* **`widget_id`** (string) – ID of the widget where the ad was shown/clicked

{% hint style="info" %}
Please make sure your webhook handler expects **exactly the same parameter names and types** as listed above.
{% endhint %}


---

# 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://tads.gitbook.io/docs/getting-started/publishers/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.