Skip to main content
Onboard customers through Kapso setup links under your own Meta app, without MPS. Kapso runs messaging; customers pay Meta fees directly.

At a glance

  1. Configure Embedded Signup and save the configuration in Kapso.
  2. Create a Kapso customer for each business you serve.
  3. Generate a setup link and let the customer connect their WhatsApp account.
  4. Confirm the connection and start messaging.
Without MPS, Kapso can’t pay Meta for your customers: each customer adds their own payment method in Meta. For managed billing with your own app, set up a Multi-partner Solution, or use Kapso’s Meta app.

Requirements

You need:

Configure Facebook Login for Business

In your Meta app:
  1. Add Facebook Login for Business if it is not already present.
  2. Open Facebook Login for Business > Configurations.
  3. Create a configuration from the WhatsApp embedded signup template when available.
  4. If you create a custom configuration, choose the WhatsApp Embedded Signup login variation.
  5. Select only the assets and permissions your customers need.
  6. Save the configuration.
  7. Copy the generated Configuration ID.
This Configuration ID is the Embedded signup config ID Kapso asks for.

Add domains for embedded signup

In Facebook Login for Business > Settings, configure the OAuth and JavaScript SDK settings required by Meta. Add the domains where customers launch setup links or embedded signup. For Kapso-hosted setup links, include the Kapso setup domain shown in the generated link, usually app.kapso.ai. If you launch setup from your own app, include your app domain too. Meta requires HTTPS domains for embedded signup.

Add the config ID in Kapso

  1. In Kapso, open Connected numbers > Meta apps.
  2. Edit or add your Meta app.
  3. Turn on Default app for embedded signup.
  4. Paste the Embedded signup config ID.
  5. Save.
Kapso setup links and reconnect flows can now use this app for embedded signup.

Create customers

Create one Kapso customer per business you serve.
Use external_customer_id to map Kapso customers back to your own database. Create a setup link for each customer.
Send the returned url to the customer or open it from your onboarding UI. To launch onboarding directly inside your own product through an active Multi-partner Solution, see Embed WhatsApp onboarding. Use allowed_connection_types to control the customer path:
  • ["dedicated"] for API-only WhatsApp Cloud API numbers
  • ["coexistence"] for customers who want to keep using the WhatsApp Business App alongside Kapso
  • ["coexistence", "dedicated"] when you want the customer to choose
If you want Kapso to provision a number during setup, add:

Detect completion

Use both redirect handling and webhooks. The success redirect can include setup details such as:
  • status
  • phone_number_id
  • business_account_id
  • display_phone_number
  • setup_link_id
For server-side reliability, subscribe to Kapso project webhooks and listen for whatsapp.phone_number.created. See Detecting WhatsApp connection and Webhooks.

Operate the customer number

After setup completes, use the customer’s phone_number_id.