---
title: "Reject Multi-Partner Solution Deactivation Request"
method: POST
path: "/{Version}/{Solution-ID}/reject_deactivation_request"
tags: ["Multi-Partner Solutions"]
---

# Reject Multi-Partner Solution Deactivation Request

`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

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.

## Path parameters

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

## Query parameters

- `fields` string

## Headers

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

## Request body

- object
  - `reject_deactivation_request` boolean, required: Set to true to reject the pending deactivation request

## Response `200`

Successfully rejected the deactivation request

- 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 parameters or malformed request
- `401`: Unauthorized - Invalid or missing access token
- `403`: Forbidden - Insufficient permissions or unauthorized access
- `404`: Not Found - Solution not found or not accessible
- `422`: Unprocessable Entity - Invalid solution state or business logic violation
- `429`: Too Many Requests - Rate limit exceeded
- `500`: Internal Server Error - Unexpected server error

---

[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)