Skip to content
Docs

Get Thread

Retrieve one inbox reply with its lead, campaign and original email.

GEThttps://api.foxreach.io/api/v1/inbox/threads/{reply_id}

Requires an API key with the read scope.

Returns the reply itself. For the full back-and-forth of sent and received messages, use Get Conversation. Reading a thread does not mark it read unless you ask.

Path Parameters#

reply_idstringpathrequired

The unique identifier of the reply.

Query Parameters#

markReadbooleanqueryDefault: false

Mark the thread as read while fetching it.

Response#

dataobject

The thread.

Show data
idstring
Reply identifier.
accountIdstring
Mailbox that received the reply.
campaignIdstring
Campaign the reply belongs to, or null.
leadIdstring
Lead the reply belongs to, or null.
fromEmailstring
Sender address.
toEmailstring
Recipient address.
subjectstring
Subject line.
bodystring
Message body as received (HTML when the sender sent HTML).
bodyPlainstring
Plain-text body.
messageIdstring
Message-ID header of the reply.
inReplyTostring
Message-ID the reply answers, or null.
categorystring
Reply category, for example interested.
isReadboolean
Whether the thread is marked read.
isStarredboolean
Whether the thread is starred.
receivedAtstring
ISO 8601 timestamp.
createdAtstring
ISO 8601 timestamp.
accountobject
id, email and displayName of the receiving mailbox. Present when the mailbox exists.
leadobject
The matched lead: id, email, firstName, lastName, company, title, phone, linkedinUrl, website, status, notes. Present when a lead matched.
campaignobject
id and name of the campaign. Present when the reply belongs to one.
originalEmailobject
The email being answered: id, subject, body, bodyPreview, fromEmail, toEmail, sentAt. Present when it is known.

Errors#

StatusDescription
401Missing, invalid, revoked or expired API key
403API key does not have the required scope: read
404Reply not found, or it belongs to another workspace

Rate Limit#

  • 100 requests per minute, per API key. Fixed 60-second window.
  • Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset (unix epoch seconds).
  • A 429 response includes a Retry-After header (seconds until the bucket resets).

For client-side patterns (Retry-After, exponential backoff, monitoring X-RateLimit-Remaining), see Rate Limiting.

Was this page helpful?
View as MarkdownLast updated November 2, 2026