What is changing in MyOperator’s webhook system and how do I migrate from GET to POST?

What is changing in MyOperator’s webhook system and how do I migrate from GET to POST?

⚡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:

  1. Create a new webhook using the POST method and JSON payload.
  2. 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

    • After Call Webhook

      Overview Webhooks are HTTP callbacks that receive notification messages for events. MyOperator uses webhooks to notify your application any time a call event happens in your account. For example, if a call has been received by your agent, you will ...

    • How to Add an In-Call Webhook in MyOperator

      ? Table of Contents What is an In-Call Webhook? Prerequisites for Adding an In-Call Webhook Step-by-Step Instructions Tips for Success Troubleshooting Frequently Asked Questions (FAQs) 1. What is an In-Call Webhook? An In-Call Webhook allows ...

    • What is a Webhook?

      A webhook lets MyOperator send event data to your server in real time. When a call or SMS event happens, we POST a JSON payload to a URL you provide. Your system can then record, route, or trigger workflows instantly. Quick answer: A webhook is an ...

    • In-Call Webhook

      Overview Webhooks are HTTP callbacks that receive notification messages for events. MyOperator uses webhooks to notify your application any time a call event happens in your account. For example, if a call has been received by your agent, you will ...

    • How a Webhook Works?

      ? Table of Contents What is a Webhook? How Does a Webhook Work? What is a Webhook Payload? How to Set Up a Webhook in MyOperator? Real-Life Example of Webhook Usage in CRM Integration Common Webhook Use Cases Troubleshooting Webhook Issues ...