> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://myoperator.crisp.help/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How do I set up and manage MyOperator Calling Webhooks?

⚡ Quick answer —
MyOperator Calling Webhooks are HTTP POST callbacks that push call-event data to your server. Three event types are available—After Call, Incall, and Disposition.

Create or edit them in MyOperator → API & Webhooks → Webhooks by specifying the event type, target URL, and (optionally) authentication headers.

---

## When should I use this guide?

Use it if you need to:

* Stream call records into a CRM or data lake
* Run automations when a call starts, ends, or is tagged with a disposition
* Update an existing webhook when your server URL or auth token changes

---

## 1. What are Calling Webhooks?

Calling Webhooks let MyOperator push call data to your application automatically—no manual export needed. Typical outcomes:

* Sync call details with your CRM.
* Kick-off workflows (e.g., open a support ticket when a call ends).
* Populate live dashboards.

---

## 2. Webhook types & use-cases

| Type | Trigger | Common use-case |
| --- | --- | --- |
| After Call | Immediately after the call ends | Store full call record (duration, agent, status). |
| Incall | While the call is live | Real-time dashboards or "screen-pop" CTI. |
| Disposition | After the call ends and the agent saves the disposition | Capture outcomes like Interested, Follow-up, Not Connected. |

---

## 3. Prerequisites checklist

* Publicly reachable HTTPS endpoint accepting POST + `application/json`.
* (Optional) Auth token or basic-auth credentials.
* MyOperator role permission: API & Webhooks access.

---

## 4. Add a new Calling Webhook

1. Log in to MyOperator.
1. Navigate to API & Webhooks → Webhooks.
1. Click Add new.
1. Select one event type: After Call, Incall, or Disposition.
1. Enter the Target URL (e.g., `https://api.example.com/hooks/myoperator`).
1. (Optional) Add auth headers or query parameters.
1. Click Save.

|| Info
Expected result: Your endpoint starts receiving HTTP POST payloads for the chosen event type.

![Adding webhooks in MyOperator](https://content.api.getguru.com/files/view/ed80e577-6daa-4634-9860-a3d88746f6ad)

![Adding webhooks in MyOperator](https://content.api.getguru.com/files/view/374a4ad8-528b-47f7-9d3c-fe70deda28fb)

---

## 5. Edit or disable an existing Calling Webhook

1. Go to API & Webhooks → Webhooks.
1. Click Edit next to the webhook.
1. Change URL, headers, or toggle Enable/Disable.
1. Click Save.

Use this whenever your server URL changes, tokens rotate, or you’re troubleshooting.

---

## 6. When webhooks do NOT fire

* Target URL down (DNS, firewall, 4xx/5xx).
* Auth tokens revoked but not updated.
* Webhook disabled or deleted.
* Endpoint rejects `application/json`.

|| Info
Retry logic: MyOperator retries 3× at 30-second intervals; after that, the event is dropped (no further retries).

---

## 7. Glossary

| Term | Definition |
| --- | --- |
| Webhook | Server-to-server callback via HTTP POST. |
| After Call | Event fired once a call ends. |
| Incall | Event fired during a live call. |
| Disposition | Agent-selected outcome after the call ends. |

---

Keywords: MyOperator webhook, After Call webhook, Incall webhook, Disposition webhook, call event API