Whatsapp config

The platform supports Meta Embedded Signup, which allows users to directly connect their WhatsApp Business accounts through a guided onboarding flow without leaving your application. This simplifies onboarding and removes the need for manual Meta Business configuration.

---

​

What is Embedded Signup

Embedded Signup is a Meta-provided flow that enables users to:

• connect their WhatsApp Business account
• grant required permissions
• complete onboarding within your platform

This flow is powered by Meta (Facebook) and requires proper app configuration and approval.

---

​

Why Embedded Signup is Used

Embedded Signup helps:

• reduce onboarding friction for users
• automate WhatsApp Business API connection
• eliminate manual Meta setup steps
• improve conversion for new users

---

​

Configuration Requirements

Before using Embedded Signup, you must:

• create a Meta App in the Meta Developer Console
• enable WhatsApp Business Platform API
• configure App ID and App Secret
• generate configuration IDs (with and without catalog)
• set up webhook verification

---

​

Required OAuth Scopes

These are the scopes the platform expects for WhatsApp OAuth / Embedded Signup:

• whatsapp_business_management
• whatsapp_business_messaging
• business_management
• catalog_management (required only when using catalog / commerce features)

Use the with catalog configuration ID when catalog_management is included, and the without catalog configuration ID when it is not.

---

​

Meta App Verification (Mandatory)

To use Embedded Signup in production, your Meta app must be verified. Verification ensures:

• your app is trusted by Meta
• permissions are approved
• users can connect their accounts without restrictions

---

​

How to Configure WhatsApp OAuth

​

Step 1: Create Meta App

1. Go to: https://developers.facebook.com/
2. Click My Apps → Create App
   
3. Enter:
   • App Name
   • Contact Email
     
4. Select Use Case as Connect with customers through WhatsApp
   
5. Select your verified Business Manager
   

​

Step 2: Add Your Product

1. Inside your app dashboard homepage, scroll below to see
2. Click Add Product
3. Select WhatsApp, Facebook Login for Business, Instagram, Messenger.
4. Complete the basic setup
   

​

Step 3: Configure App Basics

Go to App Settings → Basic Make sure to add:

• App Name and Logo
• Privacy Policy URL
• Terms of Service URL
• App Domain (your platform domain)

Then go to: Business Settings → Security Center

​

Step 4: Configure Embedded Signup

1. Go to Facebook Login for Business → Configuration
2. Click Create configuration
   
   
   
   
   
3. Create and save both configuration IDs (select scopes from Required OAuth Scopes):
   • Configuration ID (with catalog)
   
   • Configuration ID (without catalog)
   
4. Copy the below and add these values to your platform settings WhatsApp OAuth:
   • App ID
   • App Secret
   • Configuration ID
   
5. Go to WhatsApp → Configuration and add the webhook URL provided from the platform to receive all incoming WhatsApp messages. Make sure the required events are selected.
   
   

​

Step 5: Request Permissions (IMPORTANT)

Go to: App Review → Permissions and Features Request Advanced access for the scopes listed in Required OAuth Scopes.

​

Step 6: Complete App Review Sections

Go to: App Review → Settings Complete all sections:

• Branding
• Audience
• Clients
• Data Access
• Verification

All sections must be completed before submission.

​

Step 7: Submit for Review

1. Go to App Review
2. Submit requested permissions
3. Wait for Meta approval

---

​

Review Submission Pack

​

1) App Use-Case Description (Copy-Paste)

Use this when Meta asks: “Please provide a detailed description of how your app uses the permission or feature requested, how it adds value for a person using your app, and why it’s necessary for app functionality.”

​

Overall Description

Our platform helps businesses onboard to WhatsApp Business API, manage customer conversations, and run messaging workflows from a centralized dashboard. We use Meta Embedded Signup so a business can connect its own WhatsApp assets directly inside our platform with explicit user consent. The requested permissions are necessary to complete onboarding, configure business assets, enable messaging, and optionally support catalog commerce features. Without these permissions, users cannot complete account connection or use WhatsApp messaging features in our app.

​

2) Scope-by-Scope Justification (Copy-Paste)

Use the below explanations when Meta asks for justification:

​

business_management

Our platform allows businesses to connect and manage their WhatsApp Business accounts. This permission is required to access business-level assets and enable account linking via embedded signup.

​

whatsapp_business_management

This permission is required to manage WhatsApp Business account settings, phone numbers, and configurations after the user connects their account through our platform.

​

whatsapp_business_messaging

Our platform enables users to send and receive WhatsApp messages, including automated notifications, campaigns, and customer conversations. This permission is essential for message delivery and communication workflows.

​

catalog_management

This permission is used for businesses that utilize product catalogs. It allows syncing and managing catalog items for use in WhatsApp commerce features such as product messages and interactive flows.

​

3) Screen Recording Checklist

Record one complete reviewer journey (recommended 5-12 minutes):

1. Show your platform login and open Platform Settings -> WhatsApp OAuth.
2. Show app configured (mask App Secret and tokens).
3. Start Embedded Signup from platform UI.
4. Complete Meta flow and grant requested permissions.
5. Show WhatsApp account connected in the platform.
6. Send a test message from platform and show delivery/status.
7. Receive a reply and show it appears in inbox/webhook-driven view.
8. If requesting catalog_management, show a catalog-related action.

​

4) Upload Instructions

1. Upload video to Drive (public link for reviewers) or unlisted YouTube.
2. Go to Meta App Dashboard -> App Review -> Permissions and Features.
3. For each permission, paste:

• permission-specific justification
• reviewer test steps
• video URL

4. Submit with test business credentials if requested by Meta reviewer.

​

5) Pre-Submission Checklist

• App review sections (Branding, Audience, Clients, Data Access, Verification) are completed.
• Requested permissions match the Required OAuth Scopes list above.
• Embedded Signup works end-to-end in your test account.
• Video shows permission grant plus send/receive proof.
• Secrets are masked and reviewer credentials are prepared.

---

​

Important Notes

• App must be in Live Mode before production use
• Missing permissions = rejection
• Incomplete video = rejection
• Business verification is mandatory

⚠️ Need Help?
Meta verification can be complex and time-consuming.
If you need assistance, you can contact our support team.
We provide verification setup as an add-on service.

---

​

Twilio TURN Configuration (WhatsApp Calling)

To enable WhatsApp calling functionality in the platform, a TURN (Traversal Using Relays around NAT) server is required. TURN ensures stable voice connectivity, especially in restricted or NAT-based network environments. We recommend using Twilio TURN services for reliable performance.

​

Why TURN is Required

WhatsApp calling relies on WebRTC technology, which may fail in certain network conditions such as:

• firewalls blocking direct connections
• strict NAT environments
• corporate or restricted networks

TURN acts as a relay server to ensure calls are successfully connected even in these scenarios.

​

How It Works

• Twilio provides TURN credentials (temporary or generated)
• These credentials are used by the platform to establish call connections
• The TURN server relays audio data between users when direct connection fails

​

Step 1: Create Twilio Account

1. Go to: https://www.twilio.com/
2. Sign up or log in to your account
3. Navigate to Twilio Console Dashboard
4. Copy the following: Account SID & Auth Token, these will be used to authenticate TURN requests.
5. Add the following details in your platform settings: Twilio Account SID mTwilio Auth Token
6. Once added:Click Test TURN
7. The platform will automatically generate:
   • TURN URL
   • TURN Username
   • TURN Credential
     

---

​

Meta Webhook Relay

Meta Webhook Relay allows you to forward incoming WhatsApp (Meta) webhook events to another external endpoint without modifying your primary webhook configuration. This is useful when you want to duplicate or redirect webhook data to additional systems such as automation tools, CRMs, or custom APIs.

​

What this does

• receives webhook events from Meta (WhatsApp Cloud API)
• forwards the raw payload to a secondary webhook URL
• preserves original request structure and headers
• enables parallel processing of webhook events

​

Typical Use Cases

• send WhatsApp events to external automation platforms
• integrate with third-party CRMs or analytics systems
• duplicate webhook data for logging or monitoring
• trigger workflows outside the main platform

​

How It Works

1. Meta sends webhook events to your primary webhook
2. The platform captures the event
3. If relay is enabled, the same payload is forwarded to your configured URL
4. The target system receives the webhook as a standard POST request

​

Configuration Fields

• Forward URL
  The external endpoint where webhook events will be sent
• Verify Token
  Used only for webhook verification (not for forwarded events)
• Relay Toggle
  Enables or disables webhook forwarding
• Relay Scope
  Choose what to forward:
  • Messages
  • Status updates
  • Account updates

​

Important Notes

⚠️ Credit Consumption Warning

Each forwarded webhook event will consume platform credits.

• Every incoming event = 1 credit used (for forwarding)
• High message volume can increase credit usage significantly
• Monitor usage if relay is enabled in production

​

Best Practices

• Enable relay only when required
• Filter relay scope to avoid unnecessary events
• Use a reliable external webhook endpoint
• Monitor success/failure logs regularly

​

Testing

You can validate your setup using:

• Test Verification → checks webhook validation flow
• Send Meta-Style Sample → sends a sample payload to your endpoint

​

When to Use

Use Meta Webhook Relay when:

• you need multi-system integrations
• you want to extend platform functionality externally
• you are building advanced automation pipelines

​

Support

⚠️ If webhook forwarding is not working, verify your endpoint response and ensure it accepts POST requests properly.