# Sending HTTP notifications
The most versatile reporting option is the ability to send messages via the HTTP(s) protocol. By default messages are sent as a [form url encoded](https://en.wikipedia.org/wiki/Percent-encoding#The_application.2Fx-www-form-urlencoded_type) body in a request with the [POST](https://en.wikipedia.org/wiki/POST_\(HTTP\)) verb.
To use the option, you only need to provide the url to send to:
Configuring a HTTP notification
Besides the URL it is also possible to configure:
* The message body and type (JSON is supported)
* The HTTP verb used
* Conditions on when to send emails
* Conditions on what log elements to include
For details on how to customize the notification message, see the [section on customizing message content](/monitoring-and-notifications/sending-reports-via-email/custom-message-content.md).
### New in 2.0.9.106
You can now specify multiple urls, using the options:
```
--send-http-form-urls=
--send-http-json-urls=
```
These two options greatly simplify sending notifications to multiple destinations. Additionally, the options make it possible to send both the form-encoded result in text format as well as in JSON format.
---
# 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://docs.duplicati.com/monitoring-and-notifications/sending-reports-via-email/sending-http-notifications.md?ask=
```
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.