# Adding and configuring endpoints (signing secret, events, retry settings)

> Add an endpoint (where webhooks are delivered) for a customer, and change its signing secret, events and delivery settings.

Source: https://webhookadmin.com/en/docs/guide/endpoints/

## Required role and plan

- **View**: Viewer or higher
- **Add, change, delete, show the signing secret**: Developer or higher
- **Plan**: Webhook (HTTPS) on all plans. Polling and fixed source IPs on Starter and above; other destination types on Pro and above

## Add an endpoint

1. Open Endpoints in the menu and select + Add endpoint.
2. Choose the Customer (add a [customer](https://webhookadmin.com/en/docs/guide/consumers/) first).
3. Choose the Destination type (Webhook (HTTPS) by default).
4. Enter an Endpoint URL starting with https. http is allowed in the test environment.
5. Under Events, choose All or Choose. With Choose, pick at least one registered [event type](https://webhookadmin.com/en/docs/guide/event-types/).
6. Optionally turn on Send from a fixed source IP, and open More options (payload format, retries, note).
7. Select Add. Copy the signing secret (`whsec_…`) shown and set it on the receiving side.

See [Signature verification](https://webhookadmin.com/en/docs/sdk/) for how to verify signatures. You can also see the signing secret later with Show on the endpoint’s Settings tab.

## Destination types

| Type | What it does | Plan |
| --- | --- | --- |
| Webhook (HTTPS) | POSTs to the URL you enter. | All |
| Polling | The receiver fetches messages with a token, even from a network we can’t reach. | Starter and above |
| Amazon SQS, EventBridge and S3, Google Cloud Pub/Sub and Storage, Cloudflare R2, Azure Blob Storage and Service Bus, Kafka (Confluent Cloud), RabbitMQ (HTTP API) | Delivers with the credentials you enter. Use Test connection to check them first. | Pro and above |
| Slack, Microsoft Teams, Chatwork | Posts to a chat. The message is built from text, title, lines and link in the payload. No signature is added. | Pro and above |

## Create a token for a polling endpoint

1. When you add an endpoint of type Polling, its details open.
2. Check the Poller URL on the Settings tab and select Create token.
3. Enter a Name (e.g. production receiver) and create it.
4. Copy the token and set it on the receiving side. It is shown only once.

You can create up to 5 tokens per endpoint. Last polled shows when the receiver last fetched messages.

## What you can change on the Settings tab

| Item | Description |
| --- | --- |
| Events | Select Change to edit them on the Events tab. |
| Signing secret | Select Show to see it. Rotate secret issues a new secret; messages keep a signature from the old secret for 24 hours. |
| Fixed source IP | When on, messages are sent from 209.71.107.233 ([Fixed source IP](https://webhookadmin.com/en/docs/guide/fixed-ip/)). |
| Delivery order | When on, messages are delivered in order, one at a time; each waits until the previous one is delivered or fails. |
| Retries | Choose the number of retries (none, 1, 2, 3, 5, 7 or 12) and the interval (increasing, or every 1 minute, 5 minutes, 30 minutes, 1 hour or 6 hours). By default, up to 8 attempts including the first, over about 28 hours. |
| Compatibility signature | Adds one HMAC-SHA256 header for receivers that verify a custom signature. Standard Webhooks headers are always sent. |
| Transformation | Settings for [transformations](https://webhookadmin.com/en/docs/guide/transformations/) (Pro and above). |
| Payload format | Standard (wrapped in type, timestamp, data) or data only. |
| Alerts | The alert channels that cover this endpoint. |

The History tab shows changes made to this endpoint.

## Send test, pause and delete

- Send test: sends a test message to this endpoint only. Test sends do not count toward the monthly limit.
- Pause: stops delivery. Messages accepted while paused are held and sent when you select Resume (for polling endpoints, messages accepted while paused cannot be fetched).
- Delete: select Delete at the bottom of the Settings tab. Messages waiting to retry will not be sent. This cannot be undone.

## If an endpoint was disabled automatically

If deliveries keep failing for 5 days, the endpoint is disabled automatically and the reason is shown on its page. Fix the receiver, then select Resume. Messages from the time it was disabled are not delivered to this endpoint.

If a plan change removes fixed source IPs, transformations or non-webhook destination types, the endpoint is paused and its messages are held. Move to the required plan and select Resume to send them.

## Related pages

- [Customers](https://webhookadmin.com/en/docs/guide/consumers/)
- [Event types](https://webhookadmin.com/en/docs/guide/event-types/)
- [Retries and recovery](https://webhookadmin.com/en/docs/guide/retries/)
- [Fixed source IP](https://webhookadmin.com/en/docs/guide/fixed-ip/)
- [Transformations](https://webhookadmin.com/en/docs/guide/transformations/)
- [Signature verification](https://webhookadmin.com/en/docs/sdk/)