> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useinvent.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Webhooks
> Push workspace events to your own systems and watch every delivery
A webhook endpoint is a URL of yours that Invent calls when something happens in your workspace that your systems have to react to: a contact who can no longer be reached, a send that did not land, a conversation that changed hands. Instead of polling the API, your server is told.
Manage endpoints at **Settings → Webhooks**.
Each row shows the endpoint's name and URL, how many events it subscribes to, whether it is enabled, and when it was last delivered to.
This page covers managing endpoints in the app. For the payload shape, the event catalog, signature verification, and code samples, see the [Webhooks API reference](/api-reference/getting-started/webhooks).
## Creating an endpoint
Enter the **endpoint URL** that receives the requests. It has to be HTTPS, and it cannot be a private or loopback address.
The name is for you, so you can tell "Production CRM" from "Staging" at a glance.
Subscribe only to what you act on. You can change the selection later.
It is shown once, right after creation. Store it in your secret manager.
The signing secret (`whsec_…`) is displayed only on creation and on rotation. It is what proves a request came from Invent, so your handler should reject any request whose signature does not verify. If you lose the secret, rotate it to get a new one.
### The events you can subscribe to
| Group | Events |
| :---------------- | :-------------------------------------------------------------------------------------- |
| **Conversations** | `chat.assigned` |
| **Contacts** | `contact.blocked`, `contact.unsubscribed` |
| **Broadcasts** | `broadcast.failed`, `broadcast.bounced`, `broadcast.complained`, `broadcast.suppressed` |
The catalog is deliberately narrow: these are events an external system has to *act* on. Routine create and update traffic belongs to the API, not to a push feed.
## Managing an endpoint
The options menu on each row holds everything else.
| Action | What it does |
| :------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------- |
| **Edit** | Change the URL, name, or event subscriptions |
| **Send Test Event** | Delivers a signed `ping` to the endpoint and reports back whether it was accepted. The quickest way to prove your URL and signature check work |
| **View Deliveries** | The delivery log for this endpoint |
| **Disable / Enable** | Stop or resume deliveries without deleting the endpoint |
| **Rotate Secret** | Issue a new signing secret. The current one stops signing immediately, so deploy the new one first |
| **Delete** | Remove the endpoint. Events stop being delivered to it |
## Watching deliveries
**View Deliveries** lists every attempt from the last 7 days, most recent first.
Each row shows the event, the delivery status, the attempt number and the HTTP status your server returned:
* **DELIVERED**: your endpoint returned a `2xx`.
* **PENDING**: the attempt failed and a retry is scheduled.
* **FAILED**: every retry was used up.
* **SKIPPED**: the event was not sent, because the endpoint was disabled or the workspace had no balance to cover the outbound request.
Use the **replay** action on any row to send that event again. Replay is how you backfill after an outage on your side, or reprocess events once your handler is fixed.
## When deliveries fail
Failed attempts are retried on a widening schedule (5s → 5m → 30m → 2h → 5h → 10h), seven attempts in total. Requests time out after 10 seconds, so acknowledge fast and do the real work afterwards.
An endpoint that fails 30 deliveries in a row is **disabled automatically**, and the reason is shown on the endpoint. Fix your side, then enable it again, which clears the failure streak.
Delivery is at-least-once and order is not guaranteed, so make your handler idempotent and deduplicate on the event id.
## Next Steps
Payloads, headers, signature verification, and code samples
Manage endpoints programmatically instead of in the app