# Update Thread

::::callout{intent="warning"}
Inboxes are currently in private beta and only available to a limited
number of users. The response shape might change before GA.

[Get early access](https://resend.com/help?type=report\&message=I+would+like+early+access+to+Inboxes.\&priority=low) if you're interested in testing this feature.

Once you have access, upgrade your Resend SDK to use the new methods:

:::code-group
```bash Node.js
npm install resend@6.28.1-preview-inboxes.2
```

```bash CLI
npm install -g resend-cli@2.22.0-preview-inboxes.2
```
:::
::::

At least one of `read`, `folder`, or `label_id` is required.

## Path Parameters

The Inbox ID.

The Thread ID.

## Body Parameters

- `read` (boolean) — Marks every message in the thread read or unread.

- `folder` (string) — Moves the thread. One of `inbox`, `archive`, `spam`, or `trash`.

Applies this label to the thread.

## Folders

Every thread sits in exactly one folder within its inbox.

| Folder    | Meaning                                                      |
| --------- | ------------------------------------------------------------ |
| `inbox`   | The default. The thread holds at least one received message. |
| `archive` | The thread was archived.                                     |
| `spam`    | The thread was marked as spam.                               |
| `trash`   | The thread is scheduled for deletion in 30 days.             |
| `sent`    | Threads whose messages are all outbound.                     |

You can move a thread to `inbox`, `archive`, `spam`, or `trash`. `sent` is
assigned automatically.

## Response Fields

- `object` (string) — Always `inbox_thread`.

- `id` (string) — The ID of the thread.

- `subject` (string | null) — The subject of the thread.

- `folder` (string) — The folder the thread lives in after the update.

- `labels` (array) — The labels attached to the thread, each with an `id`, `name`, and `color`.

- `read` (boolean) — True only when every message in the thread is read.

:::code-group
```ts Node.js
import { Resend } from 'resend';

const resend = new Resend('re_xxxxxxxxx');

const { data, error } = await resend.inboxes.threads.update({
  inboxId: 'b3e2b2b6-3f0e-4c8e-9ad3-2f43a1e2c7f1',
  threadId: '4d8e2a1c-9b3f-4c6d-8a21-3e5f7c9c0d12',
  read: true,
  folder: 'spam',
});
```

```bash cURL
curl -X PATCH 'https://api.resend.com/inboxes/b3e2b2b6-3f0e-4c8e-9ad3-2f43a1e2c7f1/threads/4d8e2a1c-9b3f-4c6d-8a21-3e5f7c9c0d12' \
     -H 'Authorization: Bearer re_xxxxxxxxx' \
     -H 'Content-Type: application/json' \
     -d $'{
  "read": true,
  "folder": "spam"
}'
```

```bash Restore a trashed thread
curl -X PATCH 'https://api.resend.com/inboxes/b3e2b2b6-3f0e-4c8e-9ad3-2f43a1e2c7f1/threads/4d8e2a1c-9b3f-4c6d-8a21-3e5f7c9c0d12' \
     -H 'Authorization: Bearer re_xxxxxxxxx' \
     -H 'Content-Type: application/json' \
     -d $'{
  "folder": "inbox"
}'
```

```bash Apply a label
curl -X PATCH 'https://api.resend.com/inboxes/b3e2b2b6-3f0e-4c8e-9ad3-2f43a1e2c7f1/threads/4d8e2a1c-9b3f-4c6d-8a21-3e5f7c9c0d12' \
     -H 'Authorization: Bearer re_xxxxxxxxx' \
     -H 'Content-Type: application/json' \
     -d $'{
  "label_id": "7f9c1d2e-4a6b-4c3d-8e15-9b0a7c6d5e34"
}'
```

```bash CLI
resend inboxes threads update \
  --inbox_id b3e2b2b6-3f0e-4c8e-9ad3-2f43a1e2c7f1 \
  --thread_id 4d8e2a1c-9b3f-4c6d-8a21-3e5f7c9c0d12 \
  --read \
  --folder spam
```
:::

:::code-group
```json Response
{
  "object": "inbox_thread",
  "id": "4d8e2a1c-9b3f-4c6d-8a21-3e5f7c9c0d12",
  "subject": "Refund for order 1041",
  "folder": "spam",
  "labels": [],
  "read": true
}
```
:::

## Related pages

- [Account Management](./account-management-index.md)
- [API Keys](./api-keys-2-index.md)
- [API Keys](./api-keys-index.md)
- [API Reference](./api-reference-index.md)
- [AudiencesDEPRECATED](./audiencesdeprecated-index.md)
- [Authorized Apps](./authorized-apps-index.md)
- [Automations](./automations-index.md)
- [Broadcasts](./broadcasts-index.md)
- [Build with AI](./build-with-ai-index.md)
- [Changelog](../changelog.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.