# Send alarms with content using webhooks and  header attachments

As we mentioned in the previous page, a webhook is a mechanism whereby an entity on the web (e.g. a client) can notify another entity on the web (e.g. a server) when a new event that might be of interest to the other side has just occurred. 

evalink talos allows you to create and send more sophisticated webhooks to interact with the platform.

The Webhooks integration allows users to configure their webhook URLs further and transmit content to evalink talos via attachment headers. The type of the header can be a URL, an image, a widget etc. 

The structure of such a webhook is displayed below:

`https://talos.evalink.io/api/webhook-integration/incoming/`**`<webhookId>`**`?header=attachment.`**`<type>`**`:`**`<content>`**

**<https://talos.evalink.io/api/webhook-integration/incoming/\\><webhookId>**  is the URL/endpoint for a particular webhook, generated by evalink talos, as it is displayed [here](/evalink-talos/alarm-api/webhooks.md).

**\<type>** is one of the following options:

* `URL`
* `image`
* `message`
* `verification`

&#x20;**\<content>** is the relevant content for each type, e.g. the desired URL or message for the operator.

Please refer to the examples displayed below for more details.

#### Example 1 - Webhook with URL in its attachment header

```css
https://talos-app.io/api/webhook-integration/incoming/aB08421vOvbVCDlka3OHxOulD?
header=attachment.url:https://evalink.io
```

The above webhook, when invoked, will generate an alarm with the website evalink.io, as displayed in the picture below.

![](/files/-MVDqp5UMiCWJQzWiv8f)

#### Example 2 - Webhook with **an** image in its attachment header

```css
https://talos-app.io/api/webhook-ntegration/incoming/aB08421vOvbVCDlka3OHxOulD?
header=attachment.image:http://166.254.49.241:80/mjpg/video.mjpg
```

#### Example 3 - Webhook with a message in its attachment headers

```css
https://talos-app.io/api/webhook-integration/incoming/aB08421vOvbVCDlka3OHxOulD?
header=attachment.message:BuildingA-SectorB
```

#### Example 4 - Webhook with multiple URLs in its attachment headers

```css
https://talos-app.io/api/webhook-integration/incoming/aB08421vOvbVCDlka3OHxOulD?
header=attachment.url.1:https://evalink.io&
header=attachment.url.2:https://evalinklive.com

```

The above webhook, when invoked, will generate an alarm with the websites evalink.io and evalinklive.com, as displayed in the picture below.

![](/files/-MVDpf0tl3B2EjhZfU2C)

#### Example 5 - Webhook with multiple images in its attachment headers

```css
https://talos-app.io/api/webhook-integration/incoming/aB08421vOvbVCDlka3OHxOulD?
header=attachment.image.1:http://166.254.49.241:80/mjpg/video.mjpg&amp;
header=attachment.image.2:http://108.182.4.138:9000/mjpg/video.mjpg
```

#### Example 6 - Webhook with multiple messages in its attachment headers

```css
https://talos-app.io/api/webhook-integration/incoming/aB08421vOvbVCDlka3OHxOulD?
header=attachment.message.1:emergency&
header=attachment.message.2:buildingA
```

The above webhook, when invoked, will generate an alarm with the websites evalink.io and evalinklive.com, as displayed in the picture below.

{% hint style="info" %}
It is important to note that evalink talos de-duplicates the supplied resources.

This means that, for example, when you supply the same stream twice, it will show-up only once in the incoming alarm.
{% endhint %}


---

# Agent Instructions: 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://sitasys-ag.gitbook.io/evalink-talos/alarm-api/send-alarms-with-content-using-webhooks-via-header-attachments.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.