Webhook Overview

Cunnekt webhooks allow your application to receive real-time updates when messaging or platform-related events occur. Webhooks are delivered as HTTP POST requests to a webhook endpoint configured in your Cunnekt account.
A single webhook endpoint can receive updates for multiple event types, depending on the features you use.

Types of Webhooks

Cunnekt provides two categories of webhooks:

  1. Channel Webhooks

    2. Channel webhooks deliver updates related to specific messaging channels. The payload structure and fields depend on the channel.
    Examples include:

    • Inbound messages
    • Message delivery and read receipts
    • Template approval status updates

    Currently supported Channel: WhatsApp
    Check WhatsApp Webhooks

  2. Platform Webhooks

    3. Platform webhooks deliver updates related to Cunnekt’s platform behavior and automation. These webhooks are channel-agnostic.
    Examples include:

    • Conversation state changes
    • Contact creation and updates
    • Campaign lifecycle events
    • Automation and assignment updates

    Check Platform Webhooks

How Webhooks Are Delivered

When an event occurs:

  • The messaging channel or platform generates an update
  • Cunnekt forwards the update to your webhook endpoint
  • Your server processes the request and returns a response
  • Webhook requests are sent as HTTP POST requests with a JSON payload.

Webhook Configuration

You can configure your webhook endpoint from the Cunnekt dashboard:

  1. Log in to your Cunnekt account
  2. Navigate to Settings → API & Webhooks
  3. Enter your webhook endpoint URL
  4. Save the configuration

Note: Webhook endpoints must be publicly accessible over HTTPS.

Implementation Guidelines

Webhook endpoints must be designed to respond quickly and process requests asynchronously.
Before implementing webhooks, review the webhook implementation guidelines:

→ Webhook Guidelines

Sandbox vs Production

Webhook payload structure is the same for sandbox and production.
Sandbox webhooks are limited to test contacts.
Production webhooks reflect real user activity.

Security & Reliability

  • Always process webhooks aynchronously and acknowledge webhook requests with 200 OK
  • Webhooks may be retried if acknowledgment fails
  • Duplicate webhook deliveries are possible
  • Design handlers to be idempotent

Quick Links:

Review Webhook Endpoint Guidelines
View WhatsApp Webhook Payloads
View Platform Webhook Payloads