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

# Webhooks setup in Settings

> Get webhook access, open the webhook dashboard from Settings → Webhooks, and add your first endpoint. Use it before subscribing your backend to OpenCX events.

Webhooks send OpenCX events, such as a session starting or closing, a handoff, a CSAT score, or a phone call ending, to an HTTPS endpoint you run. You set up endpoints from **Settings → Webhooks**, which opens a dedicated webhook dashboard.

> [!NOTE]
>
> **Settings → Webhooks** in your [OpenCX dashboard](https://platform.open.cx/settings/webhooks). Viewing the page requires the **Webhooks** or **Settings** permission (Read). Opening the webhook dashboard requires **Webhooks** (Write).

## Get access

Webhooks are turned on per organization by OpenCX. Until they are, OpenCX sends no webhook events for your organization, and **Open dashboard** shows:

> Your organization is not allowed to use webhooks.

To request access, email the address in that message or [support@open.cx](mailto:support@open.cx). If your workspace is provided by a partner, the message shows your partner's support address instead.

## Open the webhook dashboard

**1. Open Settings → Webhooks**

Go to [Settings → Webhooks](https://platform.open.cx/settings/webhooks). The page has one section, **Webhook dashboard**: "Webhook configuration, testing and monitoring live in a dedicated dashboard."

**2. Select Open dashboard**

The webhook dashboard opens in a new browser tab. Open it again from this page whenever you need it.

## Add your first endpoint

In the webhook dashboard:

1. Add an endpoint with the HTTPS URL that should receive events.
2. Choose the events to subscribe to. Every event and its payload is listed in [Webhook event types](https://docs.open.cx/api-reference/webhooks/types.md).
3. Copy the endpoint's signing secret and verify the signature on every delivery, as described in [delivery, signatures and retries](https://docs.open.cx/api-reference/webhooks/types.md).
4. Send a test event, then check its delivery history in the dashboard.

Each delivery is an HTTP `POST` with a JSON body in the envelope `{ event, organization_id, data }`. Return a 2xx response quickly and process the event afterwards. Failed deliveries are retried automatically, and you can replay them from the dashboard.

If you use Connect, its thread and Supervisor events go through the same endpoints. See [Connect webhooks](https://docs.open.cx/connect/webhooks.md).

## Troubleshooting

| Symptom | Likely cause | Fix |
| - | - | - |
| "Your organization is not allowed to use webhooks" | Webhooks aren't turned on for your organization | Email the address in the message to request access. |
| The same message, although your organization has webhooks | Your role has **Webhooks** (Read) but not Write. The page shows this message for any failure to open the dashboard. | Ask an admin to grant **Webhooks** (Write). See the [permissions reference](https://docs.open.cx/security/permissions-reference.md). |
| No **Webhooks** entry in Settings | Your role has neither **Webhooks** nor **Settings** access | Ask an admin to grant **Webhooks** (Read or Write). |
| None of the above | Something else | Contact OpenCX support. |

***

## Related Documentation

> [card] [Webhook event types](https://docs.open.cx/api-reference/webhooks/types.md)
>
> Payloads, signatures, and retries.

> [card] [Connect webhooks](https://docs.open.cx/connect/webhooks.md)
>
> Thread and Supervisor events.

> [card] [Permissions reference](https://docs.open.cx/security/permissions-reference.md)
>
> Who can manage webhooks.

> [card] [CSAT](https://docs.open.cx/resources/csat.md)
>
> Surveys behind CSAT events.


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