Home getting started How to Use Webhooks in 360Messenger

How to Use Webhooks in 360Messenger

Last updated on Jun 23, 2026

Webhooks allow you to receive real-time updates from 360Messenger and automate your workflows. By configuring a webhook URL, you can instantly receive events such as incoming messages, message status updates, and other notifications in your application.

What Is a Webhook?

A webhook is a mechanism that sends data automatically from 360Messenger to your server whenever a specific event occurs. Instead of continuously checking for updates, your application receives information in real time.

Why Use Webhooks?

Using webhooks can help you:

  • Receive incoming messages instantly.

  • Track message delivery and status changes.

  • Automate workflows and notifications.

  • Integrate 360Messenger with your CRM, ERP, or custom applications.

  • Build real-time messaging solutions.

How to Configure a Webhook in 360Messenger

Follow these steps to set up a webhook:

  1. Sign in to your 360Messenger account.

  2. Open the Product Details section.

  3. Navigate to Webhooks.

  4. Enter your webhook URL.

  5. Save your changes.

  6. Verify that your server can receive POST requests from 360Messenger.

Supported Events

Depending on your configuration, 360Messenger can send notifications for:

  • Incoming messages

  • Outgoing messages

  • Message delivery updates

  • Read receipts

  • Connection status changes

Webhook Request Format

When an event occurs, 360Messenger sends a POST request to your webhook URL containing event information in JSON format.

Make sure your server:

  • Supports HTTPS.

  • Accepts POST requests.

  • Processes JSON payloads correctly.

  • Returns an HTTP 200 response after receiving the request.

Troubleshooting Webhook Issues

If your webhook is not receiving events:

  • Verify that the webhook URL is correct.

  • Ensure your server is publicly accessible.

  • Check that HTTPS is enabled.

  • Confirm that your application accepts POST requests.

  • Review server logs for errors.