---
title: "Accept WhatsApp Business Solution Deactivation Request"
method: POST
path: "/{Version}/{Solution-ID}/accept_deactivation_request"
tags: ["WhatsApp Business Solution Management"]
---

# Accept WhatsApp Business Solution Deactivation Request

`POST /{Version}/{Solution-ID}/accept_deactivation_request`

## Request

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

Accepts a pending deactivation request for a WhatsApp Business Multi-Partner Solution.


This endpoint completes the partner approval workflow by accepting a deactivation request
that was previously initiated by another solution partner. Upon successful acceptance,
the solution status transitions from ACTIVE to DEACTIVATED, and the pending request
status changes from PENDING_DEACTIVATION to NONE.


**Important Business Logic:**

- Solution must be in ACTIVE status with PENDING_DEACTIVATION pending status

- All outstanding payments and invoices must be settled before acceptance

- Active marketing campaigns must be concluded or transferred

- Webhook notifications will be sent to all solution partners upon completion

- Solution resources and permissions will be cleaned up according to policy

## Path parameters

- `Version` string, required
- `Solution-ID` string, required

## Query parameters

- `fields` string

## Headers

- `User-Agent` string
- `Authorization` string, required

## Request body

- object

## Response `200`

Deactivation request accepted successfully. Solution status updated to DEACTIVATED.

- WhatsAppBusinessSolution: Multi-Partner Solution details and configuration
  - `id` string, required: Unique identifier for the Multi-Partner Solution
  - `name` string, 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_app` ApplicationNode: Meta application that owns the Multi-Partner Solution
    - `id` string: Unique identifier for the Meta application
    - `name` string: Name of the Meta application
  - `owner_permissions` WhatsAppBusinessAccountPermissionTask[]: List of WhatsApp Business Account permissions granted to the solution owner

## Other responses

- `400`: Bad Request - Invalid request parameters or malformed solution ID format.
- `401`: Unauthorized - Invalid, missing, or expired access token.
- `403`: Forbidden - Insufficient permissions or app not authorized for this solution.
- `404`: Not Found - Solution ID does not exist or is not accessible to the requesting app.
- `422`: Unprocessable Entity - Valid parameters but business logic prevents processing (e.g., wrong solution state, outstanding payments).
- `429`: Too Many Requests - Rate limit exceeded. Use exponential backoff for retries.
- `500`: Internal Server Error - Unexpected server error. Retry with exponential backoff if is_transient is true.

---

[API](https://skmtc.dev/meta/apis/whatsapp-business-messaging.md) - [All operations](https://skmtc.dev/meta/apis/whatsapp-business-messaging/llms.txt) - [OpenAPI document](https://skmtc.dev/meta/apis/whatsapp-business-messaging/revisions/5c1973265369?raw)