⚡Quick answer —
MyOperator is deprecating the GET method (plus query-string parameters, non-JSON formats and old log filters).
From 28 Nov 2025, all new webhooks must be POST + JSON, and existing GET webhooks will keep firing and will automatically switch to view-only mode. Create a new POST webhook to remain fully supported.
When should I use this guide?
— Read on if you:
(a) need to create a new webhook,
(b) still rely on GET/query-string/Non-JSON patterns, or
(c) want exact dates, supported formats and the actions required by the November 2025 update.
1. Why is MyOperator updating the webhook system?
To improve security, consistency and integration performance, MyOperator is modernising its webhook framework. The new design removes outdated patterns and simplifies configuration for all users.
2. What exactly is changing?
Deprecated (becomes view-only):
- GET method
- Dynamic query-string parameters (e.g.
?caller={{mobile}}&agent={{agent_id}}) - Non-JSON content types (XML, form-data, etc.)
- Legacy log filters (Mobile/SMS based filters)
Supported now (standard going forward):
Area | New rule |
HTTP method | POST only |
Payload format | JSON only |
URL parameters | Static (no dynamic variables) |
Events | Applies to both in-call and after-call webhooks |
This POST + JSON approach avoids URL tampering, improves reliability and ensures uniform behaviour across systems.
3. Action required (if applicable)
Your webhook needs attention (it will be view-only) if it uses:
• GET method
• Dynamic query parameters
• Non-JSON formats
• Old filters
Required steps:
- Create a new webhook using the POST method and JSON payload.
- Point your endpoint to accept
Content-Type: application/json.
4. When does my GET webhook still work?
- Existing GET webhooks continue to fire exactly as before.
- After 28 Nov 2025, they become view-only. You can not edit it.
- Any webhook created on or after 28 Nov 2025 must follow the POST + JSON standard.
5. Need assistance?
If you need help migrating or identifying impacted webhooks, MyOperator Support is ready to assist.
Keywords: MyOperator webhooks, GET deprecation, POST only, JSON payload, webhook migration
Related Articles
How do MyOperator Call Disposition Webhooks work?
⚡Quick answer – A Call Disposition Webhook fires automatically when an agent adds a disposition to a call log in MyOperator. As part of the 2025 security update, all webhooks must now use HTTPS + POST + JSON and static parameters. GET, dynamic query ...
Does MyOperator’s Alerting System cover Billing, Infrastructure, and Configurable incidents?
⚡Quick answer: Yes. Our alerting system classifies incidents into Infrastructure, Billing, and Configurable categories. You can subscribe to alerts per category and choose delivery channels (email, SMS, Slack/Teams, webhook)—availability may vary by ...
What’s the difference between Contacts and Users in MyOperator, and when should I create each?
⚡ Quick answer User → Someone in your team who receives calls from your IVR or logs into the MyOperator dashboard. Requires: licence, role, extension number, and dashboard access settings. Contact → A saved phone number used for caller ID, customer ...
How to Get and Manage a MyOperator Helpline Number for Your Organisation
⚡ Quick Answer You no longer need to manually create or configure a helpline number. To get a MyOperator helpline for your organisation: 1. Sign up on the MyOperator website, or 2. Connect with your MyOperator Account Manager. The MyOperator ...
What is MyOperator?
MyOperator 1.0 was all about telephony; MyOperator 2.0 is a Business AI Operator. To reflect this evolution, we’re repositioning MyOperator across every touchpoint—from marketing to product—as an AI-powered, omnichannel communication platform. We ...