Multi-Partner Solutions
WhatsApp Business API

Accept Multi-Partner Solution Invitation

Accept an invitation to participate in a Multi-Partner Solution as a partner application. This endpoint transitions the partner's status from NOTIFICATION_SENT to ACCEPTED, enabling the solution to progress toward ACTIVE status once all required partners accept.

Use Cases:

  • Accept partnership invitations for Multi-Partner Solutions
  • Activate partner participation in existing solutions
  • Confirm partner app's commitment to solution terms and conditions
  • Enable solution workflow progression from INITIATED to ACTIVE status

Business Logic:

  • Only invited partner apps can accept solution invitations
  • Solution must be in INITIATED status to accept partnerships
  • Partner status transitions from NOTIFICATION_SENT to ACCEPTED
  • Solution may become ACTIVE once all required partners accept
  • Acceptance creates formal partnership agreement between apps

Rate Limiting: Standard Graph API rate limits apply. Use appropriate retry logic with exponential backoff.

Validation:

  • Partner app must have received a valid solution invitation
  • Solution must exist and be accessible to the partner app
  • Partner app must have proper permissions and capabilities
  • Acceptance request must include valid partner app identification
post/{Version}/{Solution-ID}/accept

Request

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

Path parameters

Versionstring required

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

Solution-IDstring required

ID of the Multi-Partner Solution to accept. This ID is provided in the original invitation and can be found in partner notifications or solution management interfaces.

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.

Request body

partner_app_idstring required

ID of the partner application accepting the solution invitation. This must match the app ID that received the original invitation.

log_session_idstring

Optional session identifier for logging and debugging purposes. Used to track the acceptance flow across multiple API calls.

Example request

{
  "partner_app_id": "9876543210987654",
  "log_session_id": "session_12345_accept_solution"
}

Response

Multi-Partner Solution invitation accepted successfully. The partner's status has been updated to ACCEPTED and the solution may progress toward ACTIVE status.

solution_idstring required

ID of the Multi-Partner Solution that was accepted

partner_status'DRAFT' | 'INITIATED' | 'NOTIFICATION_SENT' | 'ACCEPTED' | 'REJECTED' | 'DEACTIVATED' required

Current status of the partner's participation in the Multi-Partner Solution

successboolean required

Indicates whether the acceptance was successful

messagestring

Human-readable confirmation message

update_timestring date-time

Timestamp when the acceptance was processed

Example response

{
  "solution_id": "1234567890123456",
  "partner_status": "ACCEPTED",
  "success": true,
  "message": "Solution partnership accepted successfully",
  "update_time": "2024-01-15T10:30:00Z"
}

Changes

No recorded changes to this operation across all 5 revisions of this API.