Multi-Partner Solutions

Reject Multi-Partner Solution Request

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
post/{Version}/{Solution-ID}/reject

Request

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

request_type'PARTNERSHIP_REQUEST' | 'DEACTIVATION_REQUEST' required

Type of request being rejected

rejection_reasonstring

Optional reason for rejecting the request

partner_app_idstring

The app ID of the requesting partner. Required when request_type is PARTNERSHIP_REQUEST, not used for DEACTIVATION_REQUEST

Example request

{
  "request_type": "PARTNERSHIP_REQUEST",
  "rejection_reason": "Partnership terms do not align with our business requirements",
  "partner_app_id": "1234567890123456"
}

Response

Successfully rejected the Multi-Partner Solution request

successboolean required

Indicates whether the rejection was successful

solution_idstring required

The ID of the Multi-Partner Solution

rejected_request_type'PARTNERSHIP_REQUEST' | 'DEACTIVATION_REQUEST' required

Type of request that was rejected

rejection_timestampstring date-time

ISO 8601 timestamp when the rejection was processed

partner_app_idstring

App ID of the partner whose request was rejected (for partnership rejections)

Example response

{
  "success": true,
  "solution_id": "1234567890123456",
  "rejected_request_type": "PARTNERSHIP_REQUEST",
  "rejection_timestamp": "2024-01-15T10:30:00Z",
  "partner_app_id": "1234567890123456"
}

Changes

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