MM Lite Onboarding

Onboard Partners to MM Lite

Changed on

Send a request from the partner to onboard an end business to MM Lite. This creates a business agreement request and sets OBO mobility intents on eligible WhatsApp Business Accounts.

Business Flow:

  1. Validates partner business and app permissions
  2. Checks end business eligibility for MM Lite
  3. Identifies eligible shared WABAs and OBO WABAs
  4. Sets mobility intents on eligible OBO WABAs (BSPs only)
  5. Creates business agreement request
  6. Returns request ID for tracking

BSP vs TP Behavior:

  • BSPs (Business Solution Providers): Can create OBO WABAs and set mobility intents
  • TPs (Technology Partners): Can only create onboarding requests, no OBO WABA management

Rate Limiting: Subject to business partner integrations use case throttling limits. Use appropriate retry logic with exponential backoff.

Idempotency: If a pending request already exists between the same partner and end business, the existing request ID is returned instead of creating a duplicate.

post/{Version}/{Business-ID}/onboard_partners_to_mm_lite

Request

  • Base URL
    https://graph.facebook.com
  • URL
    https://graph.facebook.com/{Version}/{Business-ID}/onboard_partners_to_mm_lite
  • Auth
    HTTP bearer

Path parameters

Versionstring required

Graph API version to use for this request. Determines the API behavior and available features.

Business-IDstring required

The end business ID that will receive the MM Lite onboarding request. This is the business that the partner wants to establish an MM Lite relationship with.

Query parameters

solution_idstring

Optional WhatsApp Business Solution ID to associate with the onboarding request. If provided, the solution will be linked to the business agreement and OBO mobility intents.

Headers

User-Agentstring
Example:Meta-Business-Messaging-OpenAPI/1.0.0;spec=2025-10-21

The user agent string identifying the client software making the request.

Authorizationstring required
Example:Bearer EAABwzLixnjYBOzYmNMJJGfHq9DgNh...

Bearer token for API authentication. This should be a valid access token obtained through the appropriate OAuth flow or system user token.

Response

Successfully created MM Lite onboarding request

request_idstring required

Unique identifier for the MM Lite onboarding request

Example response

{
  "request_id": "1234567890123456"
}

Changes