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

# Webhooks

> Send every new lead straight to your CRM or another system, test the connection, and monitor deliveries.

A webhook sends each lead to a URL you choose the moment it's assigned to you, whether you won it with a bid, bought it in the [Marketplace](https://docs.usejuiced.com/customer-portal/marketplace.md), or claimed it from the [Club](https://docs.usejuiced.com/customer-portal/club.md). Point it at your CRM, a Zapier or Make hook, or your own system, and leads arrive there fresh-squeezed without anyone copying and pasting.

Find webhooks under **Notifications** → **Webhooks** in the sidebar.

![Webhooks table listing each webhook's name, URL, method, status, and last delivery](https://mintcdn.com/juicedleads/VCxKy8pKMzz2GR0H/images/portal/notifications/webhooks-light.webp?fit=max\&auto=format\&n=VCxKy8pKMzz2GR0H\&q=85\&s=652bd16c111dd01ac127fc20c761a26a)

The table shows each webhook's **Name**, **URL**, **Method**, **Status** (Active or Paused), and the result of its **Last delivery**. Click a row to see its deliveries, or use the row actions to **Pause webhook** / **Enable webhook**, **Edit webhook**, or **Delete webhook**.

## Creating a webhook

Click **New webhook**.

![New webhook form with Destination, Advanced settings, and Payload sections](https://mintcdn.com/juicedleads/VCxKy8pKMzz2GR0H/images/portal/notifications/webhook-create-light.webp?fit=max\&auto=format\&n=VCxKy8pKMzz2GR0H\&q=85\&s=33724f116e9627a16fccba5c623da274)

### Destination

* **Name** (optional) helps you tell webhooks apart, for example "CRM production".
* **URL** is where the lead data is sent.

### Advanced settings

The defaults (no authentication, POST, JSON, 10-second timeout, no extra headers) suit most CRMs. Expand **Advanced settings** if your endpoint needs something different.

| Setting | Options |
| - | - |
| **Authentication** | **None**, **Basic Auth** (username and password), or **Bearer Token** |
| **Method** | **POST**, **PUT**, or **GET** |
| **Format** | **JSON**, or **Form** (URL-encoded) |
| **Timeout** | Seconds to wait for your endpoint to respond |
| **Headers** | Extra HTTP headers to send with each request |

Saved passwords and tokens stay hidden. To change one, type a new value.

### Payload

Choose what the request contains.

* **Default payload** sends every field available for your leads in a standard shape. It's the quickest way to get started.
* **Custom payload** lets you choose fields, rename keys, and add fixed values, so the data matches what your system expects. Use **Paste JSON** to start from an example of the shape your system wants, or **Load default mapping** to start from the default and edit it.

With the default payload, each request includes the price you paid (`charged_amount`), the `scope` you won it at, when you received it (`received_on`), the `lead_type`, and all the lead's deliverable fields, such as name, email, phone, and address. Fields your provider adds later are included automatically.

Click **Create & continue to testing**. Your webhook is saved and switched on straight away, and you land on its edit page to send a test.

## Testing a webhook

Open a webhook's edit page (**Edit webhook**) and scroll to **Testing**.

![Webhook edit page with Destination, Advanced settings summary, Payload choice, and Testing options](https://mintcdn.com/juicedleads/VCxKy8pKMzz2GR0H/images/portal/notifications/webhook-edit-light.webp?fit=max\&auto=format\&n=VCxKy8pKMzz2GR0H\&q=85\&s=742014921b8404368944741052732859)

Pick the data to test with.

* **Test with a real lead** searches your leads by ID, name, email, or phone and sends exactly what that lead would send.
* **Generate sample data** fills every mapped field with fake but realistic values, which is handy before you've received any leads.
* **Add test data manually** lets you build the payload one field at a time.

Then click **Run Webhook Test**. Juiced sends the request and shows whether your endpoint **Accepted** or **Rejected** it, along with the details of the request and your endpoint's response, so you can see what went wrong.

Test deliveries don't count as real lead deliveries. They're kept on a separate **Tests** tab in the delivery history.

> [!TIP]
>
> Since new webhooks start active, run a test right after creating one. If your endpoint isn't ready yet, click **Pause** so real leads aren't sent to it until it is.

## Monitoring deliveries

Click a webhook in the table to open its overview.

![Webhook overview with delivery stats, a delivery history table with response codes and durations, and the webhook's details](https://mintcdn.com/juicedleads/VCxKy8pKMzz2GR0H/images/portal/notifications/webhook-detail-light.webp?fit=max\&auto=format\&n=VCxKy8pKMzz2GR0H\&q=85\&s=9b610eb77abf224307ef4a398b6faf87)

* **Stats** cover the last 30 days, with **Total deliveries**, **Success rate**, **Failed**, **Average duration**, and **Last delivery**.
* **Deliveries** lists every attempt, with **Live** and **Tests** tabs. Each row shows when it was sent, the lead, the result and response code with how long it took, and a delivery ID. Filter by **Result** or **Delivery date**, and click a row to see the full request and response, including headers and body.
* **Details** shows the endpoint, method, format, trigger (**Lead assigned**), and webhook ID.

Use **Pause** / **Enable** and **Edit** at the top of the page to change the webhook.

### Re-sending a delivery

If a delivery failed (say your CRM was down), click **Redeliver** on that row to send the lead again. Juiced uses the webhook's current settings, so if you fixed the URL, authentication, or payload since, the re-send uses the fixed version.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.