Step aside — we are finished with this thread
POST/api/conversations/:conversationId/thread-control/release
NOT THE SAME AS PASSING (38 §I1.6). Passing names a successor; releasing names nobody and sets the thread IDLE. Meta's own examples are an app that has answered everything it can, and one that cannot answer this particular question and steps aside so the default app may.
The consequence is worth stating because the caller cannot see it: Meta is explicit that "Only the default application can send messages in this state", and which app is the default lives in Facebook Page Setup, a screen no API exposes. If this workspace is not the default, releasing means it cannot write again until the customer does. The panel says so before the click.
Request
Responses
- 200
- 401
- 403
- 404
- 422
The refreshed conversation, whose capabilities say whether this panel may still write.
Not authenticated. code: account_disabled means the member's seat was deactivated in this workspace: the session is over even though the token was not revoked (clients sign out and clean up).
Authenticated but not allowed.
Resource not found (or not visible to the current tenant).
This conversation cannot be handed over (no Page behind the channel, no platform id for the contact), or Meta refused — its own sentence is in detail.