> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hooksnode.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Destinations

> The endpoints that get your events.

A destination is an HTTPS URL that gets events from a project. Each destination has its own queue, attempts and log.

## Add a destination

Open **Destinations → Add destination** in your project.

| Setting       | Notes                                                                                   |
| ------------- | --------------------------------------------------------------------------------------- |
| Name          | A label, for example `Ledger`.                                                          |
| URL           | Your endpoint. Private addresses are refused.                                           |
| Sources       | Pro only. Pick the sources this destination takes events from. Empty means all sources. |
| Filter        | Optional. See [Filters](/destinations/filters).                                         |
| Transform     | Optional. See [Transforms](/destinations/transforms).                                   |
| Extra headers | Optional. See [Extra headers](/destinations/extra-headers).                             |
| Signing       | Off by default. See [Signing](/destinations/signing).                                   |
| Active        | Turn a destination off to stop deliveries without deleting it.                          |

## The request that hooksnode sends

| Part    | Value                                                                  |
| ------- | ---------------------------------------------------------------------- |
| Method  | The method of the incoming request. Mail and polled events use `POST`. |
| Body    | The event body, after the transform.                                   |
| Headers | See below.                                                             |
| Timeout | 15 seconds.                                                            |

hooksnode builds the headers in this order. A later step replaces a header of the same name.

1. The headers of the incoming request.
2. The destination's extra headers.
3. `X-Hooksnode-Source-Id: <source-id>`.
4. `X-Hooksnode-Signature: sha256=<hex>`, if signing is on.

## Success and failure

* A `2xx` response is a success. hooksnode stores up to 1 MiB of the response body.
* Anything else is a failed attempt. See [Retries](/delivery/retries).

## Test before you save

The destination editor has a **Test** panel. Paste a sample body. hooksnode runs your transform and filter and shows the output, whether the filter matched, and any error. Nothing is sent.

## Health checks

Every 15 minutes, hooksnode sends a `HEAD` request to each destination, with a 5 second timeout. A `5xx` or no answer is `unhealthy`. A `4xx` is `degraded`. Anything else is `healthy`.

## Limits

| Plan | Destinations per project |
| ---- | ------------------------ |
| Free | 5                        |
| Pro  | 50                       |