Get inbox thread
Beta. This endpoint is in beta. Behavior, parameters, and response shapes may change without notice.
Returns a single thread including the ordered message history.
Authorizations
Authenticate every request with a Bearer token. Pass your Reply API key in the
Authorization header:
Authorization: Bearer <your-api-key>Get your API key from the Reply dashboard: Settings → API Key.
Path Parameters
x >= 1Response
Inbox thread
Full inbox thread with the contact, channel-specific account ids, sequence, category, meeting-intent flag, and the ordered list of messages.
unknown, email, linkedIn Contact party on the other end of an inbox thread.
Two shapes are possible, distinguished by the isDeleted flag:
- Live contact (
isDeleted: false) —idandownerIdreference the live contact record;fullName,email,linkedInProfileUrl,phone,companyName,titlecome from the live record (any may still benullif the corresponding field is unset on the contact, e.g.emailisnullfor a LinkedIn-only contact). - Deleted contact (
isDeleted: true) — the underlying contact record has been removed, soidandownerIdarenull. The remaining identifying fields (fullName,email,linkedInProfileUrl,phone,companyName,title) are populated from the snapshot stored on the thread when it was created — typically enough for the user to recognise who the thread was with even though the contact no longer exists in their workspace.
Email message within an inbox thread.
- Inbox Email Message
- Inbox LinkedIn Message
Whether the thread is marked as read by the current user.
Email account that owns this thread. null for non-email threads.
LinkedIn account that owns this thread. null for non-LinkedIn threads.
Minimal sequence reference attached to an inbox thread.
The thread's single pending AI-drafted reply, if one is awaiting review. null when the thread has no active AI draft.
Minimal category reference embedded in thread responses.
Whether the thread has been flagged as carrying meeting intent (manually or via AI detection).