Assign exactly this set of labels to a thread
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
50Response
Successful Response
Which surface a conversation happens on.
Threads are contact-scoped, not channel-scoped, so this says how a thread is REACHED rather than partitioning the inbox: a reply arrives, is classified and stops the cadence identically either way, and only the send path differs.
email, linkedin INB-09: whether an explicit channel='linkedin' reply can go out on this thread — it carries a LinkedIn member identity and a paired account. The composer's channel toggle keys off this.
INB-08: the contact's LinkedIn profile URL, when our own evidence (invitation ledger, dispatched actions, or the sequence's mapped column) names one. Only the SINGLE-thread read resolves it; the list leaves it null.
§79: the contact's enrolment in this thread's sequence, when it has one — the id the 'Resume cadence' action targets.
INB-04: an AI reply is waiting for approval on this thread — the list row's 'Action required' mark. Only the thread LIST populates it; single-thread reads leave it False and the open conversation fetches the draft itself.
§63: the matched message, headlined around the match. Only set when searching.
INB-12: hidden from the working views until this instant.
§79: set when the cadence is stopped (reply, unsubscribe, bounce, ...). None for a live or normally-completed enrolment. Only 'reply' is resumable.
reply, unsubscribe, bounce, manual, company_reply, row_left_audience, step_removed, removed