# Get Thread
> Retrieve one inbox reply with its lead, campaign and original email.
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](/api-reference/inbox/get-thread). Reading a thread does not mark it read unless you ask.
## Path Parameters
The unique identifier of the reply.
## Query Parameters
Mark the thread as read while fetching it.
## Response
The thread.
Reply identifier.
Mailbox that received the reply.
Campaign the reply belongs to, or `null`.
Lead the reply belongs to, or `null`.
Sender address.
Recipient address.
Subject line.
Message body as received (HTML when the sender sent HTML).
Plain-text body.
Message-ID header of the reply.
Message-ID the reply answers, or `null`.
Reply category, for example `interested`.
Whether the thread is marked read.
Whether the thread is starred.
ISO 8601 timestamp.
ISO 8601 timestamp.
`id`, `email` and `displayName` of the receiving mailbox. Present when the mailbox exists.
The matched lead: `id`, `email`, `firstName`, `lastName`, `company`, `title`, `phone`, `linkedinUrl`, `website`, `status`, `notes`. Present when a lead matched.
`id` and `name` of the campaign. Present when the reply belongs to one.
The email being answered: `id`, `subject`, `body`, `bodyPreview`, `fromEmail`, `toEmail`, `sentAt`. Present when it is known.
```bash cURL
curl -X GET "https://api.foxreach.io/api/v1/inbox/threads/rpl_abc123?markRead=true" \
-H "X-API-Key: otr_your_key"
```
```python Python SDK
from foxreach import FoxReach
client = FoxReach(api_key="otr_your_key")
thread = client.inbox.get("rpl_abc123", mark_read=True)
```
```typescript TypeScript SDK
import { FoxReach } from "foxreach";
const client = new FoxReach({ apiKey: "otr_your_key" });
const thread = await client.inbox.get("rpl_abc123", { markRead: true });
```
```json
{
"data": {
"id": "rpl_abc123",
"accountId": "cea_abc123",
"campaignId": "cmp_abc123",
"leadId": "lead_abc123",
"fromEmail": "jane@acme.com",
"toEmail": "outreach@company.com",
"subject": "Re: Quick question",
"body": "Sounds interesting, can we talk Thursday?
",
"bodyPlain": "Sounds interesting, can we talk Thursday?",
"messageId": "",
"inReplyTo": "",
"category": "interested",
"isRead": true,
"isStarred": false,
"receivedAt": "2026-10-30T14:12:00+00:00",
"createdAt": "2026-10-30T14:12:05+00:00",
"account": { "id": "cea_abc123", "email": "outreach@company.com", "displayName": "John from Company" },
"campaign": { "id": "cmp_abc123", "name": "Q4 outreach" }
}
}
```
## Errors
| Status | Description |
|--------|-------------|
| `401` | Missing, invalid, revoked or expired API key |
| `403` | API key does not have the required scope: `read` |
| `404` | Reply 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](/rate-limiting).