WhatsApp Configuration

• Introduction
• Prerequisites
• Accessing WhatsApp Configuration
  • Navigation Path
• WhatsApp Webhook Configuration
  • Step 1: Enter Meta Application Details
  • Marketing Messages API Routing Bundle v1.2.1+
  • Step 2: Connect Webhook
  • Step 3: Verify Connection
  • Webhook Event Subscriptions

Introduction

What it does: Connects your SaaS platform to the WhatsApp Cloud API, enabling automated message sending and receiving for all users. Handles webhook setup and integration for seamless communication. Why it's useful: Provides essential WhatsApp messaging features to your SaaS customers, allowing real-time engagement and automation. Ensures your platform can deliver and receive messages reliably at scale. Location: Super Admin Panel → WhatsApp → Webhook Configuration

When to Use This Page

This page is only required if you are using the Embedded Signup Addon and have Meta Tech Provider approval from Meta. In that case, configure your Meta application details and connect the webhook from here. Otherwise, webhook configuration is handled on the tenant side and no setup is needed here.

Prerequisites

Before configuring WhatsApp in your SaaS platform:

• Create a Meta Business Account at business.facebook.com
• Set up a WhatsApp Business API account
• Create a Facebook App in the Meta for Developers portal
• Have your Facebook App ID and App Secret ready (found in your Meta for Developers app settings)

Accessing WhatsApp Configuration

Navigation Path

1. Login to Super Admin Panel
2. Navigate to WhatsApp Webhook → Webhook Configuration

WhatsApp Webhook Configuration

Step 1: Enter Meta Application Details

Enter your Meta application credentials:

• Facebook App ID (required) – Your Facebook App ID from the Meta for Developers portal
• Facebook App Secret (required) – Your Facebook App Secret from the Meta for Developers portal
• Facebook Config ID (for Embedded Signup) – Only required if you are using the Embedded Signup Addon and have Meta Tech Provider approval from Meta. Otherwise, leave this field empty.

Facebook Config ID

The Facebook Config ID field is only for Meta Tech Providers who have received approval from Meta and are using the Embedded Signup addon. If this does not apply to you, leave the field empty.

Embedded Signup v4 configuration required

Meta stopped accepting Embedded Signup v2 and v3 configurations on 15 October 2026. The Facebook Config ID must come from an Embedded Signup v4 configuration that includes the Cloud API and Marketing Messages API for WhatsApp products.

If your Config ID was created before this change, create a new configuration and paste its ID here. See Facebook Login Configuration.

Click Save Configuration to save your settings.

Marketing Messages API Routing Bundle v1.2.1+

This switch decides how marketing templates are sent for all tenants on your platform. It is on by default.

• On: Marketing templates are sent through Meta's Marketing Messages API (MM Lite). If a tenant has not accepted Meta's terms yet, Meta still delivers their messages through the regular Cloud API. Utility and Authentication templates always use the regular Cloud API.
• Off: Every template is sent through the regular Cloud API. Tenants see a message on their Marketing Messages API card saying the administrator has turned it off.

Keep this switch on unless you have a specific reason to turn it off.

To see what tenants see, read Marketing Messages API.

Step 2: Connect Webhook

After saving your App ID and App Secret, scroll down to the Webhook Connection section.

1. Click the Connect Webhook button
2. The system will automatically create and register the webhook with Meta — there is no need to manually go to the Meta Developer portal to configure the webhook
3. Once connected, the Connection Status will change to Connected

Automatic Webhook Setup

WhatsMarkSaaS handles the entire webhook registration process automatically. Simply enter your App ID and App Secret, save the configuration, and click Connect Webhook. No manual webhook setup on the Meta Developer portal is required.

Step 3: Verify Connection

After connecting, you can click the Verify button to confirm the webhook is properly registered and receiving events from WhatsApp's servers.

Webhook Event Subscriptions

Once the webhook is connected, the system automatically subscribes to the events it needs. You do not need to subscribe to any of these events in the Meta Developer portal yourself:

• messages – Receives incoming messages and message delivery statuses
• message_template_status_update – Syncs template approval/rejection status
• message_template_quality_update – Syncs template quality changes
• template_category_update – Syncs template category changes
• account_update – Receives account changes. For example, Meta uses it to tell WhatsMark when a tenant accepts the Marketing Messages API terms, so the tenant's status updates automatically.

Daily status check

WhatsMark also checks the Marketing Messages API status of every connected tenant once a day. This check runs through the Laravel scheduler, so your server's cron job must be running.

Template Sync

Without these subscriptions, template status and category changes will not sync automatically to tenant accounts. Tenants would need to manually reload templates to get the latest status and category information.