Multi-Partner Solutions

Reject Multi-Partner Solution Deactivation Request

Reject a pending deactivation request for a Multi-Partner Solution. This endpoint allows solution partners to decline deactivation requests from solution owners, maintaining the solution in its current active operational state.

Use Cases:

  • Reject deactivation requests from solution owners
  • Maintain active solution partnerships when deactivation is not appropriate
  • Respond programmatically to deactivation requests through API integration
  • Keep solutions operational when business requirements or partnerships change

Business Logic:

  • Solution status remains ACTIVE after successful rejection
  • StatusForPendingRequest transitions from PENDING_DEACTIVATION to NONE
  • All existing solution configurations and permissions are preserved
  • Solution partners receive notifications about the rejection decision

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

Permissions: Requires whatsapp_business_management permission and valid solution partnership relationship.

post/{Version}/{Solution-ID}/reject_deactivation_request

Request

  • Base URL
    https://graph.facebook.com
  • URL
    https://graph.facebook.com/{Version}/{Solution-ID}/reject_deactivation_request
  • 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

Your Multi-Partner Solution ID with a pending deactivation request. This ID is provided when you create the solution and can be found in your Partner Dashboard or through solution management APIs.

Query parameters

fieldsstring

Comma-separated list of fields to include in the response. If not specified, default fields will be returned (name, status, status_for_pending_request). Available fields: id, name, status, status_for_pending_request, owner_app, owner_permissions

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

reject_deactivation_requestboolean required

Set to true to reject the pending deactivation request

Example request

{
  "reject_deactivation_request": true
}

Response

Successfully rejected the deactivation request

idstring required

Unique identifier for the Multi-Partner Solution

namestring required

Human-readable name of the Multi-Partner Solution

status'DRAFT' | 'INITIATED' | 'ACTIVE' | 'REJECTED' | 'DEACTIVATED' required

Current effective status of the Multi-Partner Solution

status_for_pending_request'PENDING_ACTIVATION' | 'PENDING_DEACTIVATION' | 'NONE' required

Status of any pending solution status transition requests

owner_permissionsWhatsAppBusinessAccountPermissionTask[]

List of WhatsApp Business Account permissions granted to the solution owner

Example response

{
  "id": "1234567890123456",
  "name": "E-commerce Integration Solution",
  "status": "ACTIVE",
  "status_for_pending_request": "NONE",
  "owner_app": {
    "id": "9876543210987654",
    "name": "Solution Partner App"
  },
  "owner_permissions": [
    "MANAGE",
    "DEVELOP",
    "MANAGE_TEMPLATES"
  ]
}

Changes

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