Get this Meta thread back

POST 
/api/conversations/:conversationId/thread-control/take

TAKING AND ASKING ARE DIFFERENT NEWS (38 §I1.2). Meta permits a takeover only where the business has switched Conversation Routing on AND set the takeover toggle in Page Setup → Advanced Messaging; everywhere else the only legal verb is request, which asks the tool currently holding the thread.

This endpoint tries the takeover and falls back to asking on Meta's refusal — Meta's own answer being more authoritative than any field we could read. A 200 means the thread is ours and the composer opens. A 202 with requested: true means we ASKED and the current owner decides: ownership is deliberately not recorded, because a request is not a grant.

Request

Responses

200

The refreshed conversation, whose capabilities say whether this panel may still write.

202

A takeover was not permitted, so control was REQUESTED instead. The conversation comes back unchanged — we do not own it yet.

401

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

403

Authenticated but not allowed.

404

Resource not found (or not visible to the current tenant).

422

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.