> For the complete documentation index, see [llms.txt](https://docs.duplicati.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplicati.com/monitoring-and-notifications/sending-reports-via-email/sending-http-notifications.md).

# Sending HTTP notifications

This page describes how to send reports via the HTTP protocol

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:

<figure><img src="https://2363712449-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7cMJiGuXy340g9NzpxLY%2Fuploads%2Fgit-blob-e704628db7123fdbf8da9a38034911f5a79bd99f%2FScreenshot%202024-11-20%20at%2014.50.14.png?alt=media" alt=""><figcaption><p>Configuring a HTTP notification</p></figcaption></figure>

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.

### Retries and certificates

If the request fails, it is retried `--send-http-retries` times (default `3`), waiting `--send-http-retry-delay` (default `1s`) between attempts.

For servers with a self-signed certificate, use `--send-http-accept-specified-ssl-hash=<sha1 hash>` to accept that specific certificate. `--send-http-accept-any-ssl-certificate` accepts any certificate and should only be used for testing, and `--send-http-ignore-revocation-failure` ignores failures to check whether the certificate is revoked.

To send the progress of running operations instead of a report when they finish, see [Sending live status reports](/monitoring-and-notifications/sending-reports-via-email/sending-live-status-reports.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplicati.com/monitoring-and-notifications/sending-reports-via-email/sending-http-notifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
