Multi-Partner Solutions

Send Multi-Partner Solution Deactivation Request

Submit a deactivation request for a Multi-Partner Solution. This initiates a workflow to transition the solution from its current state to deactivated, following proper business validation and approval processes.

Use Cases:

  • Request deactivation of an active Multi-Partner Solution
  • Initiate solution lifecycle transition management
  • Trigger business workflow for solution deactivation approval
  • Programmatically manage solution lifecycle states

Business Logic:

  • Solution must be in ACTIVE or INITIATED state to be eligible for deactivation
  • Deactivation requests are processed asynchronously
  • Solution status will transition to PENDING_DEACTIVATION during processing
  • Final deactivation requires business approval workflow completion

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

Workflow:

  1. Validate solution ownership and permissions
  2. Check solution eligibility for deactivation
  3. Submit deactivation request to business workflow
  4. Return confirmation with tracking identifier
post/{Version}/{Solution-ID}/send_deactivation_request

Request

  • Base URL
    https://graph.facebook.com
  • URL
    https://graph.facebook.com/{Version}/{Solution-ID}/send_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. This ID is provided when you create the solution and can be found in your Partner Dashboard or through solution management APIs.

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

reasonstring

Optional reason for the deactivation request

Example request

{
  "reason": "Solution no longer needed for current business operations"
}

Response

Successfully submitted deactivation request

successboolean required

Indicates whether the deactivation request was successfully submitted

messagestring required

Human-readable message describing the result

request_idstring

Unique identifier for tracking the deactivation request

Example response

{
  "success": true,
  "message": "Deactivation request submitted successfully",
  "request_id": "deactivation_req_1234567890"
}

Changes

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