LogoLogo
Become a PartnerStatus Page
  • get started
    • Welcome to 360Dialog
    • Quickstarts
      • Register as a Meta Tech Provider
      • Add a WhatsApp Number
      • Set up Integrated Onboarding
      • Create a Message Template
      • Send a Message
      • (temp title) Getting started as a partner
    • Pricing & Billing
      • Payment Methods for BR: Pix & Boleto
      • Month Closing Invoice (MCI)
    • Get API Access
    • Tech Provider Program
      • Understanding the Meta Tech Provider Program
      • Becoming a Meta Tech Provider: A Step-by-Step Guide
  • MM Lite Beta Program
    • Onboarding
    • Sending Messages
    • Expected Errors & Programming Languages
    • MM Lite Sandbox Testing
      • Sending Messages using MM Lite Sandbox
      • Expected Erros & Programming Languages
  • Partner & Account Management
    • Solutions for Partners
      • Benefits for Partners
      • Partner Hub
      • WABA Management
    • Account Setup & Management
      • Prerequisites and best practices for account creation
      • Account Structure
      • Account Creation
  • Integrations & API Development
    • Webhook Events & Setup
      • Webhook Events (Partner & Messaging API)
      • Webhook Configuration & Management
    • Integration Best Practices
      • Architecture and Security
      • Best Practices for Designing Integrations
        • Design a Stable Webhook Receiving Endpoint
      • Sizing Your Environment Based on Expected Throughput
      • Design a Resilient Message Sending Service
      • Integrated Onboarding
        • Basic Integrated Onboarding
        • Custom Integrated Onboarding
        • Host Your Own Embedded Signup
      • API Key Authentication for the Partner API
  • API Reference
    • Messaging API
    • Messaging Health Status
    • Sandbox (Test API Key)
    • Differences Between Cloud API and On-Premise API for Partners
      • [will be deprecated] Messaging with On-Premise API
    • Partner API
  • WABA Management
    • Managing WABA Accounts
      • Using the Partner Hub to manage Clients and Channels
      • Using the Partner API to manage Clients and Channels
      • Partner Permission to Generate API Key
      • Checking Usage & Statistics
    • Phone Number & Hosting
      • Migrating a Phone Number
        • Migrate number from Meta or alternate BSP to 360Dialog
        • Migrate a phone number to a new WABA
        • Migrate a phone number to a new WABA to change messaging Currency
      • WhatsApp Coexistence
        • Coexistence Onboarding
        • Coexistence Webhooks
      • Hosting type Change (On-premise API to Cloud API)
    • WABA Profile & Compliance
      • Display Name Guidelines
      • WABA Profile Info
      • WABA Policy Enforcement
      • Business Account Verification
    • Partner change (between 360Dialog Partners)
    • WhatsApp Flows
    • Accelerated Onboarding
    • Business Account Verification
  • Messaging
    • Sending & Receiving Messages
      • Conversations
      • Receiving messages
      • Before sending a message
    • Message Types
      • Conversational Components
      • Checklist for Message Broadcasts and Campaigns
      • Text messages
      • Interactive messages
        • Single and Multi Product Messages
        • Location Request Messages
        • Address Messages (India and Singapore only)
      • Contacts & Location Messages
    • Template Messages
      • Template Library
      • Template Elements
      • Sending Template Messages
      • Authentication Templates
        • Zero-Tap Authentication Templates
        • One-Tap Autofill Authentication Templates
        • Copy Code Authentication Templates
      • Catalog Templates
      • Product Card Carousel Templates
      • Single-Product Message Templates
      • Coupon Code Templates
      • Limited-Time Offer Templates
      • Multi-Product Templates
    • Media Messages
      • Upload, retrieve or delete media
    • Messaging Health & Troubleshooting
      • Messaging Limits & Quality Rating
      • Errors While Messaging
      • Messages statuses
  • Commerce & Payments
    • Payments (India Only)
      • Receive WhatsApp Payments via Payments Gateway
      • Receive WhatsApp Payments via Payment Links
      • Order Details Template Message
    • Payments (Singapore Only)
      • Receive WhatsApp Payments via Stripe
    • Products and Catalogs
      • India Businesses: Compliance for Commerce
  • Support & Updates
    • Help & Troubleshooting
      • FAQ
      • Error Code Reference
      • User Support Documentation
        • Tutorials
          • Page How to Troubleshoot Login Issues in the 360dialog Hub
          • How to Report an Issue
          • How to Contact Support
        • How-To Guides
          • Raise a support request
          • Requesting a Status Update for Business Verification
        • Reference
          • Troubleshooting Embedded Signup Issues
          • Commerce Policy Checks for WhatsApp API Access
          • Support Availability & SLAs
          • Incident Issue Prioritization
          • Case Types Table
        • Explanation
          • Why Business Verification Takes Time
          • Why Some Issues Are Not Emergencies
          • Understanding the Support Process
      • Support with Meta
    • Imprint & Data Privacy
    • Product Updates & News
      • How to ensure your Template Messages will be received
      • Integrated Onboarding new look and Campaigns Best Practices
Powered by GitBook
On this page
  • Requirements
  • Tech Provider registration and approved Solution
  • Technical capacity to host and manage your own Embedded Signup
  • Cloud API enabled
  • Set Partner Hub Webhook URL and listen to Webhook Events
  • Building the Integration
  • Step 1: Create or retrieve a Client Account
  • Step 2: Surface Embedded Signup to client and fetch information
  • Step 3: Connect Client account to registered Phone Number
  • Step 4: Create API key to start messaging

Was this helpful?

  1. Integrations & API Development
  2. Integration Best Practices
  3. Integrated Onboarding

Host Your Own Embedded Signup

PreviousCustom Integrated OnboardingNextAPI Key Authentication for the Partner API

Last updated 2 months ago

Was this helpful?

For even more personalization, if you are an approved Meta Tech Provider, you can also host your own Embedded Signup flow.

Requirements

Tech Provider registration and approved Solution

To enable this option, you must be a Meta approved Tech Provider and have a live Solution with 360dialog.

See more details in our documentation.

Technical capacity to host and manage your own Embedded Signup

You will also need to be able to host and manage your own Embedded Signup script, which requires technical knowledge. We will not be able to support you on troubleshooting your own Embedded Signup.

Request Advanced Access for public_profile permission

To host your own embedded signup, you must add extra permission for the process to work smoothly. In the Meta for Developers App dashboard > navigate to your App Review > Permissions > Find the ‘public_profile’ permission and request advanced access.

Ensure advanced access is granted before configuring the ES.

Cloud API enabled

As announced in November 2023, Meta is transitioning to a fully Cloud-hosted WhatsApp Business Platform and will stop supporting On-Premise API in October 2025. Starting from On-Premise client v2.53, all new feature updates will be exclusively delivered to Cloud API. While the On-Premise API client will receive quarterly releases, they will focus solely on bug fixes and security patches.

Set Partner Hub Webhook URL and listen to Webhook Events

Building the Integration

Step 1: Create or retrieve a Client Account

Create client account

POST https://hub.360dialog.io/api/v2/partners/{partner_id}/account_sharing/clients

Request example curl --request POST --url https://hub.360dialog.io/api/v2/partners/partner_id/account_sharing/clients --header 'Accept: application/json' --header 'Authorization: Bearer 123' --header 'Content-Type: application/json' --data '{ "name": "string", "email": "string", "user_name": "string"}'

Request Body

Name
Type
Description

name*

string

Name of the client user

email*

string

Email address of the client user.

user_name*

string

Name of the client user.

{
  "id": "string", // ID of the Client
  "created_at": "string",
  "created_by": {
    "user_id": "string",
    "user_name": "string"
  },
  "modified_at": "string",
  "modified_by": {
    "user_id": "string",
    "user_name": "string"
  }
}

Step 2: Surface Embedded Signup to client and fetch information

Step 3: Connect Client account to registered Phone Number

Use the endpoint below to submit the phone number/channel to 360dialog records. If the number was successfully onboarded via self-hosted Embedded Signup and the attached client_id matches the user data in 360dialog records, the onboarding flow end by redirecting the Client to the Partner Redirect URL set.

Submit channel/number created via self-hosted Embedded Signup

POST https://hub.360dialog.io/api/v2/partners/{partner_id}/account_sharing/numbers

Request example curl --request POST --url https://hub.360dialog.io/api/v2/partners/partner_id/account_sharing/numbers --header 'Accept: application/json' --header 'Authorization: Bearer 123' --header 'Content-Type: application/json' --data '{ "solution_id": "string", "waba_external_id": "string", "waba_business_id": "string", "client_id": "string", "tier": "string" }'

Path Parameters

Name
Type
Description

partner_id*

string

Request Body

Name
Type
Description

solution_id*

string

Your approved Solution ID

waba_business_id

string

The Client's Business Manager ID

waba_external_id*

string

The WABA ID returned through the ES callback.

client_id

string

The ID of the client

tier

string

Can be used to set the default pricing plan for the number to be added.

Will only work for partners enabled for tiered pricing. *If you are not sure of you billing plan, please reach out to our Support Team.

Clients on partners with client payment will be able to change the pre-selected plan.

Allowed values: regular, premium

Default: regular

Use the tier parameter to set the pricing plan. If no value is provided, numbers will be connected with regular pricing plan as default.

{
  "solution_id": "string",
  "waba_external_id": "string",
  "waba_business_id": "string",
  "client_id": "string",
  "tier": "regular",
  "message": "string"
}

If the process is successful message field will return Success. Please wait, your number is onboarding. If not, the usual error response will be returned.

{
  "meta": {
    "success": false,
    "http_code": 400,
    "developer_message": "Can not add number! Waba account with id {waba id} already added to the system and belongs to another partner/client."
  }
}

{
  "meta": {
    "success": false,
    "http_code": 404,
    "developer_message": "Partner/Tech provider with this solution id not found!"
  }
}

Step 4: Create API key to start messaging

You should be able to generate an API Key and connect it to your integration to start messaging with this phone number by default.

This option is only available.

.

In order to later submit the number, you need to either retrieve an existing client_id or create a new client instance through our Partner API using the endpoint below. Make sure to store the Client ID of each client within your database, since it will be required afterwards. Alternatively, you can also retrieve it with .

When the is completed by the client, you can use the code received in the payload to fetch detailed WABA information. See more and .

When the number is fully live, you will receive the .

See for details.

See differences between On-premise API and Cloud API
Learn how to change hosting type of registered numbers
Embedded Signup
here
here
Channel Live Webhook Event
Partner Permissions
Understanding the Meta Tech Provider Program
Tech Provider Program
Enable Cloud API in your Partner Hub to be able to register Cloud API numbers
if your Partner Hub is already enabled for Cloud API
this endpoint
See instructions here