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

# Reject Multi-Partner Solution Request

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

## Request

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

Reject a pending partnership request or deactivation request for a Multi-Partner Solution.
This endpoint allows solution owners to decline incoming requests and maintain control
over their solution partnerships and lifecycle.


**Use Cases:**
- Reject partnership requests from unauthorized or incompatible applications
- Decline deactivation requests to keep solutions active
- Maintain solution security and partnership quality
- Control solution access and collaboration boundaries


**Request Types:**
- `PARTNERSHIP_REQUEST`: Reject an incoming partnership request from another app
- `DEACTIVATION_REQUEST`: Reject a request to deactivate the solution


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


**Business Logic:**
- Only solution owners can reject requests for their solutions
- Partnership rejections require the partner_app_id parameter
- Rejection actions are permanent and cannot be undone through this API
- Rejected requests may need to be resubmitted through proper channels

## Path parameters

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

## Headers

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

## Request body

- SolutionRejectRequest: Request payload for rejecting a Multi-Partner Solution request
  - `request_type` 'PARTNERSHIP_REQUEST' | 'DEACTIVATION_REQUEST', required: Type of request being rejected
  - `rejection_reason` string: Optional reason for rejecting the request
  - `partner_app_id` string: The app ID of the requesting partner. Required when request_type is PARTNERSHIP_REQUEST, not used for DEACTIVATION_REQUEST

## Response `200`

Successfully rejected the Multi-Partner Solution request

- SolutionRejectResponse: Successful response for solution rejection operation
  - `success` boolean, required: Indicates whether the rejection was successful
  - `solution_id` string, required: The ID of the Multi-Partner Solution
  - `rejected_request_type` 'PARTNERSHIP_REQUEST' | 'DEACTIVATION_REQUEST', required: Type of request that was rejected
  - `rejection_timestamp` string, date-time: ISO 8601 timestamp when the rejection was processed
  - `partner_app_id` string: App ID of the partner whose request was rejected (for partnership rejections)

## Other responses

- `400`: Bad Request - Invalid parameters or malformed request
- `401`: Unauthorized - Invalid or missing access token
- `403`: Forbidden - Insufficient permissions or not solution owner
- `404`: Not Found - Solution ID does not exist or request not found
- `422`: Unprocessable Entity - Request cannot be processed due to business logic constraints
- `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)