GUgupshup
Operate — Thread Control

Pass or release thread control

A dedicated Partner Portal route, not part of the /bizai/** catch-all. The Postman collection's /bizai/thread_control is only a sub-path the catch-all would forward; use this one.

Partner Portal forwards the body unchanged to WASS, which fills phone_number_id from the app and calls Meta POST /{phone_number_id}/thread_control. Passing control changes who answers a live conversation. release hands it back and, per Meta, emits no handover webhook.

Meta errors on this route are Graph-style ((#100) ..., code 2494191 when take is not permitted), not the {title, detail} envelope used on /bizai/**.

Rate limit: 500 requests per 60 seconds per app, separate from /bizai/**. Only application/json is accepted (415 otherwise).

post/partner/app/{appId}/thread/control

Request

  • Base URL
    https://partner.gupshup.io
  • URL
    https://partner.gupshup.io/partner/app/{appId}/thread/control
  • Auth
    API key in header Authorization

Request body

messaging_product'whatsapp' required
tostring required

Consumer phone number.

action'pass' | 'release' | 'take' required
metadatastring

Optional context passed to the new owner.

Response

Control changed. Meta documents {"messaging_product":"whatsapp"}; the Partner Portal source's OpenAPI example shows {"success": true}. Neither has been observed on this route.

messaging_product'whatsapp'
successboolean

Changes

No recorded changes to this operation across all 1 revision of this API.