⚡Quick answer -
An In-Call Webhook is an HTTPS POST that MyOperator fires while a call is still in progress (ringing or answered). Configure it under APIs & Webhook › Calling Webhooks › Add new, choose “InCall”, paste your public HTTPS endpoint, save, and verify you receive the JSON shown below.
Read this if you need real-time call data (caller ID, status, IVR ID, etc.) pushed to a CRM, help-desk, or automation service without polling the MyOperator API.
MyOperator emits a POST to your endpoint at each call-state change.
Alt-text: Sequence diagram showing MyOperator sending two POSTs (ringing & answered) to your server.
• Real-time data: caller, agent list, call state.
• Trigger CRM pop-ups or routing rules before the call connects.
• Customisable payload—send only the fields you need.
• Works for Peer-to-Peer and IVR flows.
Requirement | Why it matters |
MyOperator admin login | Only admins can add webhooks |
Public HTTPS endpoint | HTTP is rejected |
Ability to accept JSON POST | Body is |
Optionally: auth header/token | To verify the origin |
Tip: You can use https://webhook.site for first-time testing.
Field | Meaning |
uid | Unique call ID |
clid | Caller number (E.164) |
call_state | 0=ringing, 1=answered |
event | 1=start, 2=update |
users | Agent numbers handling call |
public_ivr_id | IVR flow identifier |
Alt text: Adding and configuring a new webhook
Expected outcome: MyOperator webhook log shows “Delivered” and your endpoint returns HTTP 200.
• Custom header: x-myop-signature: <token> – Validate HMAC on your server.
• Basic Auth: Set username:password@host in the URL.
• IP allow-list: Open firewall to MyOperator IP range 103.21.77.0/24.
• URL uses HTTP instead of HTTPS.
• Endpoint takes > 5 s to respond (MyOperator retries 3×, then marks failed).
• Server is private/VPN-only—must be publicly reachable.
Symptom | Likely cause | Fix |
No POST received | DNS / firewall | Verify public DNS, port 443 open |
“Webhook failed” in the dashboard | 4xx/5xx response | Endpoint must reply 2xx |
Duplicate payloads | Endpoint slow | Send early 200, process async |
Still stuck? Email support@myoperator.com with your Webhook ID and failed log screenshot.
Keywords: MyOperator, In-Call Webhook, real-time call data, API Integration, JSON payload, HTTPS, CRM popup, webhook security, troubleshooting