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
- Log in to MyOperator.
- Navigate to API & Webhooks → Webhooks.
- Click Add new.
- Select one event type: After Call, Incall, or Disposition.
- Enter the Target URL (e.g.,
https://api.example.com/hooks/myoperator). - (Optional) Add auth headers or query parameters.
- Click Save.
Expected result: Your endpoint starts receiving HTTP POST payloads for the chosen event type.
5. Edit or disable an existing Calling Webhook
- Go to API & Webhooks → Webhooks.
- Click Edit next to the webhook.
- Change URL, headers, or toggle Enable/Disable.
- 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.
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
Updated on: 19/01/2026