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

# Endpoints

> Creating and managing webhook endpoints, subscribing to events, testing, and the delivery log.

# Endpoints

An endpoint is a destination URL plus the set of events it should receive.

## Creating an endpoint

From **Settings → Webhooks → Endpoints**, click **Add Endpoint** and provide:

* **Endpoint Name** — a label to help you tell endpoints apart.
* **Endpoint URL** — the `https://` URL the CRM will POST to.
* **Subscribed Events** — checked from a grouped list (Clients, Leads, Invoices, and so on). Only
  checked events are delivered to this endpoint. See the **[Event reference](/events)** for the
  full list.

Once saved, the endpoint is **active** and a **signing secret** is generated for it automatically —
see **[Verification](/verification)**.

## Editing and deleting

Edit an endpoint to change its name, URL, or subscribed events at any time. Deleting an endpoint
removes its subscriptions and its entire delivery log — this cannot be undone.

## Sending a test event

Open an endpoint's detail page and use **Send Test Event** to pick one of its subscribed events and
queue a single delivery with synthetic example data. This is the fastest way to confirm your
receiving server is reachable and your signature verification code is correct before relying on
real CRM activity.

Test deliveries are clearly synthetic (`"id": 0` and a placeholder message) — real customer data is
never used for a test send.

## The delivery log

Every attempted delivery — real or test — appears in the endpoint's delivery log with:

* The event key
* Status (**Pending**, **Success**, or **Exhausted**)
* The HTTP response code returned by your server (if any)
* Number of attempts made
* The timestamp of the last attempt
* The exact JSON payload that was sent (expand **View** to inspect it)

## Resending a delivery

Any delivery — including one that already succeeded — can be manually resent from the log with the
resend button. This resets its attempt count and queues it for immediate delivery, which is useful
after fixing an issue on your receiving server without waiting for the original CRM event to happen
again.

## Re-enabling a disabled endpoint

If an endpoint was automatically disabled after repeated failures, fix the underlying issue on your
server, then edit the endpoint and save it again — saving reactivates it. New deliveries will resume
being sent.