---
title: "Get inbox threads for a contact"
method: GET
path: "/v3/contacts/{id}/inbox-threads"
tags: ["Contacts"]
---

# Get inbox threads for a contact

`GET /v3/contacts/{id}/inbox-threads`

<Info>
  **Beta.** This endpoint is in beta. Behavior, parameters, and response shapes may change without notice.
</Info>

<small>_Requires the `contacts:read` scope (or a broader one that includes it)._</small>

Use this endpoint when you need the email conversation threads exchanged with a contact, grouped as they appear in your inbox. Results are paged with the top and skip query parameters.

## Path parameters

- `id` integer, required

## Query parameters

- `top` integer
- `skip` integer

## Response `200`

Contact inbox threads retrieved successfully

- object
  - `items` object[], required
    - `id` integer, required
    - `channel` 'unknown' | 'email' | 'linkedIn', required
    - `isRead` boolean, required
    - `subject` string, nullable — Subject of the last message in the thread (email only).
    - `lastActivityDate` string, date-time, required
    - `sequence` object, nullable — Minimal sequence reference attached to an inbox thread.
      - `id` integer, required
      - `name` string, required
    - `category` object, nullable — Minimal category reference embedded in thread responses.
      - `id` integer, required
      - `name` string, required
    - `hasMeetingIntent` boolean, required
    - `status` object, required — Aggregated thread state, derived from the latest message.
      - `state` 'ok' | 'needsAttention', required — Thread-level status: - `ok` — nothing requires user attention. - `needsAttention` — the latest outbound message failed to send and the thread needs review.
  - `hasMore` boolean, required — Indicates if there are more items to fetch

## Other responses

- `400` — Route-parameter validation failure (e.g. non-positive `id`) or a business rule rejection (e.g. invalid pagination).
- `401` — Unauthorized. The response body is empty; check the `WWW-Authenticate` header for the expected scheme.
- `403` — Inbox feature is not available for this user or team.
- `404` — Contact not found
- `429` — Too Many Requests

---

[API](https://skmtc.net/reply/apis/reply-api.md) · [All operations](https://skmtc.net/reply/apis/reply-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/reply/reply-api/revisions/1c3d32eaf95e/schema)