--- title: "client.threads()" description: "Every method in this namespace: its signature, its parameters, what it returns and an example." url: "https://openemail.uk/docs/java/reference/threads" area: "Java" category: "Reference" --- # client.threads() Every method in this namespace: its signature, its parameters, what it returns and an example. ## Methods Read, search, label, trash, snooze, mute and delete conversations in the mailbox, with their attachments, notes and summaries, read the inbox one tab at a time, and choose the tab the mail of a sender always goes to. ### `threads().list` List one page of threads in a folder ```java Page list(RequestOptions options) ``` Returns one page of threads from the mailbox index, ordered by each thread's latest message with the newest first unless `sort` says otherwise. A row is only `object` and `id`, so call `get` for the messages, labels and unread state. `sort`, `dateFrom`, `dateTo` and `fromContacts` are the thread list's own controls: the four orders, a date range read against the newest message on each thread, and a filter to mail from saved contacts. Every order pages to the end, and a cursor carries on in the order it was handed out in, so send the same filters with it. `folder` defaults to `inbox` and is matched against label ids after being upper cased, so `sent`, `archive`, `spam`, `trash`, `draft`, `snoozed`, `starred` and `unread` all work, `bin` is read as `trash`, and a user label id works as a folder too. A name that matches nothing returns an empty page rather than an error. `labelIds` narrows the folder further: a thread must carry the folder label and every id you pass. `category` keeps one inbox tab, `primary`, `promotions`, `updates`, `social` or `forums`, where `primary` is every thread in no other tab. `query` takes the mailbox search syntax. Plain words must all appear, and each matches loosely: case, accents and separators are ignored and part of a longer word counts, so `min` finds "Benjamin". A quoted phrase is matched as written apart from case and accents, so `"ben jamin"` does not find "Ben-Jamin" while `"quarterly invoice"` finds "Quarterly invoice". When nothing matches exactly, close spellings are returned instead, so `benjimin` finds "Benjamin": a plain word, or the value of `from:`, `to:`, `cc:`, `subject:`, `body:`, `filename:` or `label:`, may differ from the start of a word by one typo when it has four to seven letters and by two when it has eight or more, while a quoted phrase, a word containing a digit, a shorter word and an excluded word still match exactly, and the pages that follow keep matching the same way. Filler words such as `the`, `about` or `emails` are dropped from a list of plain words when something else is left to search for, so `emails from john` searches for `john` alone. Operators such as `from:`, `to:`, `subject:`, `label:`, `is:unread`, `has:pdf`, `after:2026/01/31` and `newer_than:7d` narrow it, and `OR`, parentheses and a leading `-` combine them. `is:muted` finds muted threads, `is:waiting` the threads with a reminder nobody has answered yet, and `category:promotions` one inbox tab in any folder. Recipients are stored as one list without roles and never hold a Bcc, so `cc:` reads the same field as `to:` and `bcc:` matches nothing of its own. `from:me` is mail you sent, and `to:me` is mail carrying one of your own addresses, aliases included, among its recipients or as the address it was delivered to. With `RequestOptions.of("semantic", true)` the plain words of `query` match by meaning rather than spelling. Describe the mail in a few words, `flight to Berlin` or `invoices I still owe`, in any language, and the threads closest in meaning come back best match first, together with every thread the words match as text, which ranks above one that only means the same. A thread is kept only when it is clearly closer to the words than the rest of the mailbox, so a description nothing fits returns only the text matches. Operators and filters narrow it as usual, `sort` does not apply, and a query with no plain words is a text search whatever `semantic` says. Meaning is read from the whole conversation, newest messages first, so an earlier message counts too, and a workspace that turned search by meaning off in its settings gets a text search instead. Words and the `from:`, `to:`, `cc:`, `subject:` and `body:` operators read only the newest message on each thread: its sender, its recipients, its subject and the first 4,000 characters of its body with markup stripped. `filename:` and `has:` read every attachment on the whole conversation, and `label:`, `in:` and `is:` read the whole conversation. A plain word also matches the name of any attachment on the conversation, whichever message carried it. A sealed message has no body text to match. The search stays inside `folder` unless the query names a folder itself, with `in:` or a folder `is:` such as `is:sent`, and `in:anywhere` searches every folder, on its own as well as beside other terms. A drafts listing is the exception and stays in drafts whatever the query names. Dates read the newest activity on the thread, in UTC. `after:` includes the day it names and `before:` excludes it, and a date can be written `YYYY/MM/DD`, `YYYY-MM-DD`, `YYYYMMDD`, as a bare year, or as epoch seconds or milliseconds. A short date reads day first (`16/09/2026`), unless the second number cannot be a month (`09/16/2026`), and a number above 12 settles it either way. The API pages with an opaque `pageToken`, which the SDK hands back as `nextCursor` and accepts as `cursor`. Scopes: `threads:read`. **Parameters** - `options.folder` (`String`): Label the threads must carry, case insensitive. Defaults to `inbox`, and `bin` is read as `trash`. - `options.query` (`String`): Mailbox search. Plain words must all appear and match loosely, a quoted phrase has to appear as written, filler words are dropped when something else is left to search for, and operators such as `from:ada`, `has:pdf` and `in:anywhere` narrow it. - `options.labelIds` (`String or List`): Label ids a thread must all carry on top of `folder`, matched exactly. A map is sent comma separated. - `options.sort` (`String`): `newest` (the default), `oldest`, `sender` or `subject`, the four orders of the thread list in the app, as in `uk.openemail.constants.ThreadSorts`. `sender` and `subject` are alphabetical, newest first within one sender or subject. - `options.dateFrom` (`Instant or String`): Keeps threads whose newest message arrived at or after this instant. An `Instant` or an ISO 8601 string with a time and an offset. - `options.dateTo` (`Instant or String`): Keeps threads whose newest message arrived at or before this instant. Both ends are included, and `dateFrom` after `dateTo` is a 422. - `options.fromContacts` (`boolean`): When true, keeps only threads whose newest message came from a saved contact. A key limited to some addresses reads the contacts its owner saved. - `options.semantic` (`boolean`): When true, the plain words of `query` match by meaning instead of spelling, in any language, and the closest threads come first along with every thread the words match as text. Operators and the other filters still apply and `sort` does not. Ignored when the workspace has search by meaning turned off. - `options.category` (`String`): Keeps only the threads sorted into this inbox tab: `primary`, `promotions`, `updates`, `social` or `forums`, as in `uk.openemail.constants.InboxCategories`. `primary` is every thread in no other tab. In `query`, `category:promotions` filters the same way in any folder. - `options.address` (`String`): Keeps only the threads delivered to this address, the address filter of the thread list. One the key does not reach returns nothing rather than failing. - `options.limit` (`int`): Threads per page, a whole number from 1 to 100. Defaults to 25. - `options.cursor` (`String`): The `nextCursor` of the previous page, passed back unchanged. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A `Page` of maps with `items`, `hasMore` and `nextCursor`. Each item has `object` set to `thread` and `id`. **Example** ```java Page page = client.threads().list(RequestOptions.create().set("folder", "inbox").set("query", "from:ada has:pdf").limit(50)); for (Map thread : page) { System.out.println(thread.get("id")); } if (page.hasMore()) { System.out.println("Next page: " + page.nextCursor()); } ``` **Notes** - The server offers a cursor whenever a page comes back full, so `hasMore` can be true on what turns out to be the last page, and the next call then returns no items. - Threads that arrived in the same instant are ordered by id, so a page boundary between two of them never skips or repeats one. - A thread that receives mail while you page moves ahead of the cursor and is not returned by later pages. - A value `query` cannot use is ignored rather than narrowing, so a typo in a value widens the result instead of emptying it. That covers `larger:`, `smaller:`, `size:`, `messagesize:`, `list:`, `rfc822msgid:`, `received:` and `sent:`, a `category` naming no inbox tab, a `has:` word naming no kind of attachment, an `importance:` other than `high` or `low`, an unreadable date and a duration whose unit is not `h`, `d`, `w`, `m` or `y`. An operator name it does not know, `project:` for instance, is searched as plain text. - A narrowed key only sees threads delivered to the addresses it covers, every address on a whole domain it holds included. A thread still has to carry the folder and every one of `labelIds`, the same as for any other key. Also available in: API [`GET /threads`](https://openemail.uk/docs/api/reference/threads#get-threads); TypeScript [`threads.list()`](https://openemail.uk/docs/sdk/reference/threads#list); Python [`threads.list()`](https://openemail.uk/docs/python/reference/threads#list); Ruby [`threads.list`](https://openemail.uk/docs/ruby/reference/threads#list); PHP [`threads->list`](https://openemail.uk/docs/php/reference/threads#list); Go [`Threads.List`](https://openemail.uk/docs/go/reference/threads#list); C# [`Threads.ListAsync`](https://openemail.uk/docs/csharp/reference/threads#list); CLI [`openemail threads list`](https://openemail.uk/docs/cli/reference/threads#threads-list). ### `threads().listAll` Collect every thread in a folder into one list ```java List> listAll(RequestOptions options) ``` Walks every page with the same filters as `list` and returns once the last page is in, so the whole result sits in memory at once. That suits a label view or a small folder. For a large inbox, `iterate` lets you stop as soon as you have what you need. Each request asks for `limit` threads, 25 when you leave it out, so raising it to 100 needs a quarter of the round trips. Passing `cursor` starts the walk from that page instead of the first. The walk ends when the server stops offering a cursor or hands back the one it was given. A failure on any page throws out of the call and discards everything collected so far. Scopes: `threads:read`. **Parameters** - `options.folder` (`String`): Label the threads must carry, case insensitive. Defaults to `inbox`. - `options.query` (`String`): Mailbox search, as in `list`. Plain words must all appear and match loosely, a quoted phrase has to appear as written, filler words are dropped when something else is left to search for, and operators such as `from:ada`, `has:pdf` and `in:anywhere` narrow it. - `options.labelIds` (`String or List`): Label ids a thread must all carry on top of `folder`, matched exactly. - `options.sort` (`String`): `newest` (the default), `oldest`, `sender` or `subject`, the four orders of the thread list in the app, as in `uk.openemail.constants.ThreadSorts`. `sender` and `subject` are alphabetical, newest first within one sender or subject. - `options.dateFrom` (`Instant or String`): Keeps threads whose newest message arrived at or after this instant. An `Instant` or an ISO 8601 string with a time and an offset. - `options.dateTo` (`Instant or String`): Keeps threads whose newest message arrived at or before this instant. Both ends are included, and `dateFrom` after `dateTo` is a 422. - `options.fromContacts` (`boolean`): When true, keeps only threads whose newest message came from a saved contact. A key limited to some addresses reads the contacts its owner saved. - `options.semantic` (`boolean`): When true, the plain words of `query` match by meaning instead of spelling, in any language, and the closest threads come first along with every thread the words match as text. Operators and the other filters still apply and `sort` does not. Ignored when the workspace has search by meaning turned off. - `options.category` (`String`): Keeps only the threads sorted into this inbox tab: `primary`, `promotions`, `updates`, `social` or `forums`, as in `uk.openemail.constants.InboxCategories`. `primary` is every thread in no other tab. - `options.address` (`String`): Keeps only the threads delivered to this address, the address filter of the thread list. One the key does not reach returns nothing rather than failing. - `options.limit` (`int`): Page size for each request, a whole number from 1 to 100. Defaults to 25. - `options.cursor` (`String`): A `nextCursor` to start the walk from instead of the first page. - `options.apiKey` (`String`): Overrides the client's API key for every page of this walk. **Returns** A list of maps, every matching thread with `object` set to `thread` and its `id`, newest first. **Example** ```java List> snoozed = client.threads().listAll(RequestOptions.create().set("folder", "snoozed").limit(100)); for (Map all : snoozed) { System.out.println(all.get("id")); } ``` **Notes** - Each page is its own request with its own retries, so a network blip on page five does not restart the walk from page one. - Rows are ids only. Reading the threads afterwards is one `get` per id. Also available in: API [`GET /threads`](https://openemail.uk/docs/api/reference/threads#get-threads); TypeScript [`threads.listAll()`](https://openemail.uk/docs/sdk/reference/threads#listAll); Python [`threads.list_all()`](https://openemail.uk/docs/python/reference/threads#listAll); Ruby [`threads.list_all`](https://openemail.uk/docs/ruby/reference/threads#listAll); PHP [`threads->listAll`](https://openemail.uk/docs/php/reference/threads#listAll); Go [`Threads.ListAll`](https://openemail.uk/docs/go/reference/threads#listAll); C# [`Threads.ListAllAsync`](https://openemail.uk/docs/csharp/reference/threads#listAll). ### `threads().iterate` Stream threads one at a time across pages ```java PagedIterable iterate(RequestOptions options) ``` Returns a `PagedIterable` that yields threads one by one and requests the next page only when the current one is used up. Nothing is fetched until the loop starts, and breaking out of it stops further requests, so this is the way to scan a large folder for the first match. Filters behave as in `list`, and each request asks for `limit` threads, 25 by default. The cursor marks a position in time rather than a row count, so trashing, archiving or relabelling threads inside the loop does not make the walk skip the ones after them. A thread that receives new mail during the walk moves ahead of the cursor and is not yielded again. With `RequestOptions.of("semantic", true)` the cursor counts places in the ranked list instead, so moving a thread out of the folder during the walk can shift the ones after it. Scopes: `threads:read`. **Parameters** - `options.folder` (`String`): Label the threads must carry, case insensitive. Defaults to `inbox`. - `options.query` (`String`): Mailbox search, as in `list`. Plain words must all appear and match loosely, a quoted phrase has to appear as written, filler words are dropped when something else is left to search for, and operators such as `from:ada`, `has:pdf` and `in:anywhere` narrow it. - `options.labelIds` (`String or List`): Label ids a thread must all carry on top of `folder`, matched exactly. - `options.sort` (`String`): `newest` (the default), `oldest`, `sender` or `subject`, the four orders of the thread list in the app, as in `uk.openemail.constants.ThreadSorts`. `sender` and `subject` are alphabetical, newest first within one sender or subject. - `options.dateFrom` (`Instant or String`): Keeps threads whose newest message arrived at or after this instant. An `Instant` or an ISO 8601 string with a time and an offset. - `options.dateTo` (`Instant or String`): Keeps threads whose newest message arrived at or before this instant. Both ends are included, and `dateFrom` after `dateTo` is a 422. - `options.fromContacts` (`boolean`): When true, keeps only threads whose newest message came from a saved contact. A key limited to some addresses reads the contacts its owner saved. - `options.semantic` (`boolean`): When true, the plain words of `query` match by meaning instead of spelling, in any language, and the closest threads come first along with every thread the words match as text. Operators and the other filters still apply and `sort` does not. Ignored when the workspace has search by meaning turned off. - `options.category` (`String`): Keeps only the threads sorted into this inbox tab: `primary`, `promotions`, `updates`, `social` or `forums`, as in `uk.openemail.constants.InboxCategories`. `primary` is every thread in no other tab. - `options.address` (`String`): Keeps only the threads delivered to this address, the address filter of the thread list. One the key does not reach returns nothing rather than failing. - `options.limit` (`int`): Page size for each request, a whole number from 1 to 100. Defaults to 25. - `options.cursor` (`String`): A `nextCursor` to start from instead of the first page. - `options.apiKey` (`String`): Overrides the client's API key for every page of this walk. **Returns** A `PagedIterable` that yields one map per thread, each with `object` set to `thread` and `id`. **Example** ```java for (Map summary : client.threads().iterate(RequestOptions.create() .set("folder", "inbox") .set("query", "receipt newer_than:30d") .limit(100))) { System.out.println(summary.get("id")); } ``` **Notes** - The generator is lazy, so an abandoned loop costs only the pages it consumed. Also available in: API [`GET /threads`](https://openemail.uk/docs/api/reference/threads#get-threads); TypeScript [`threads.iterate()`](https://openemail.uk/docs/sdk/reference/threads#iterate); Python [`threads.iterate()`](https://openemail.uk/docs/python/reference/threads#iterate); Ruby [`threads.iterate`](https://openemail.uk/docs/ruby/reference/threads#iterate); PHP [`threads->iterate`](https://openemail.uk/docs/php/reference/threads#iterate); Go [`Threads.Iterate`](https://openemail.uk/docs/go/reference/threads#iterate); C# [`Threads.IterateAsync`](https://openemail.uk/docs/csharp/reference/threads#iterate). ### `threads().get` Read a thread with every message on it ```java Map get(String id, RequestOptions options) ``` Returns the whole conversation, oldest message first, with the labels the thread sits in and its unread state. Unsent draft replies are included in `messages` with `isDraft` set to `true`, which is why `messageCount`, the length of `messages`, can be higher than `totalReplies`, which counts only real messages. Messages are passed through as the mailbox stored them, so each message is an open map rather than a fixed field list. The one field the API commits to is `encryption`. When `encryption.format` is `pgp-mime`, `pgp-inline` or `smime-encrypted`, the message is sealed and its body is empty or holds armour, which `OpenEmail.isSealed(message)` checks for you. `pgp-signed` and `smime-signed` are ordinary readable mail. A message with no `encryption` at all was stored before detection existed, so its absence says nothing about whether it was plaintext. Each message's `tags` and `unread` are overwritten on read with the thread's current labels and unread flag, so they describe the thread and not that one message. Scopes: `threads:read`. **Parameters** - `id` (`String`, required): Thread id, as returned by `list` or carried on a message. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `id` echoed from the request, `messages`, `labels` as maps with `id`, `name` and `color`, `messageCount`, `hasUnread`, `totalReplies` and `deliveredTo`, the workspace address the thread belongs to (null when none was recorded). **Example** ```java Map thread = client.threads().get("CAHk7pQ2x9LmZ4-mail.example.com"); System.out.println(thread.get("messages") + " " + thread.get("labels")); ``` **Notes** - A thread delivered to no address the key covers is a 404, exactly like one that does not exist. - `hasUnread` mirrors the `UNREAD` label, and `update` with `read` is how you change it. - Draft ids from `drafts().list` open here too, because a draft is stored as a thread labelled `DRAFT`. Also available in: API [`GET /threads/{id}`](https://openemail.uk/docs/api/reference/threads#get-threads-id); TypeScript [`threads.get()`](https://openemail.uk/docs/sdk/reference/threads#get); Python [`threads.get()`](https://openemail.uk/docs/python/reference/threads#get); Ruby [`threads.get`](https://openemail.uk/docs/ruby/reference/threads#get); PHP [`threads->get`](https://openemail.uk/docs/php/reference/threads#get); Go [`Threads.Get`](https://openemail.uk/docs/go/reference/threads#get); C# [`Threads.GetAsync`](https://openemail.uk/docs/csharp/reference/threads#get); CLI [`openemail threads get`](https://openemail.uk/docs/cli/reference/threads#threads-get). ### `threads().update` Mark a thread read or unread and change its labels ```java Map update(String id, Map patch, RequestOptions options) ``` Adds and removes labels on a thread in one call. `read` is shorthand for the `UNREAD` label: `true` removes it and `false` adds it. At least one of `read`, a non empty `addLabelIds` or a non empty `removeLabelIds` is required, each list takes at most 50 ids, and any other key is a 422 because the body is strict. Folders are labels too, so archiving is `"addLabelIds", ["ARCHIVE"]` with `"removeLabelIds", ["INBOX"]`, the same pair the app uses. `TRASH`, `SNOOZED` and `DRAFT` are refused in either list with 422 `label_not_directly_settable`, because each needs a step this route cannot take. Use `trash` and `snooze` for those. User label ids come from `labels().list`, and the system ids such as `ARCHIVE`, `STARRED` and `UNREAD` are taken in any case. An id in `addLabelIds` that names no label is refused with 422 `label_not_found` and nothing on the thread changes, so create the label with `labels().create` first. An unknown id in `removeLabelIds` is not an error, since the thread cannot carry it. Removals are applied before additions, so an id in both lists ends up on the thread. Scopes: `threads:write`. **Parameters** - `id` (`String`, required): Thread id. - `patch.read` (`boolean`): `true` removes `UNREAD`, `false` adds it. - `patch.addLabelIds` (`List`): Label ids to put on the thread, at most 50, each naming a label, never `TRASH`, `SNOOZED` or `DRAFT`. - `patch.removeLabelIds` (`List`): Label ids to take off the thread, at most 50, never `TRASH`, `SNOOZED` or `DRAFT`. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `id`, `addedLabelIds` and `removedLabelIds`. Both lists echo the request, with system ids upper cased, plus the `UNREAD` change that `read` implies, not what actually changed. **Example** ```java Map updated = client.threads().update("CAHk7pQ2x9LmZ4-mail.example.com", Body.of( "read", true, "addLabelIds", List.of("ARCHIVE", "USER_RECEIPTS"), "removeLabelIds", List.of("INBOX") )); System.out.println(updated.get("addedLabelIds") + " " + updated.get("removedLabelIds")); ``` **Notes** - The SDK retries this call after a network failure or a retryable status, which is safe because adding a label already present or removing one already gone changes nothing. - The thread is looked up before the body is validated, so a wrong id is a 404 even when the patch is also invalid. - User label ids look like `USER_RECEIPTS`. Take them from `labels().list` rather than building them. Also available in: API [`PATCH /threads/{id}`](https://openemail.uk/docs/api/reference/threads#patch-threads-id); TypeScript [`threads.update()`](https://openemail.uk/docs/sdk/reference/threads#update); Python [`threads.update()`](https://openemail.uk/docs/python/reference/threads#update); Ruby [`threads.update`](https://openemail.uk/docs/ruby/reference/threads#update); PHP [`threads->update`](https://openemail.uk/docs/php/reference/threads#update); Go [`Threads.Update`](https://openemail.uk/docs/go/reference/threads#update); C# [`Threads.UpdateAsync`](https://openemail.uk/docs/csharp/reference/threads#update); CLI [`openemail threads update`](https://openemail.uk/docs/cli/reference/threads#threads-update). ### `threads().trash` Move a thread to the Bin ```java Map trash(String id, RequestOptions options) ``` Adds `TRASH` and removes `INBOX`, `SPAM`, `SNOOZED` and `ARCHIVE` in one step, which is what the app's delete does. Doing half of that through `update` would leave the thread listed in both the Bin and its old folder, which is why `update` refuses `TRASH`. Nothing is deleted. The thread stays readable with `get` and lists under `RequestOptions.of("folder", "trash")`. Calling this on a thread that is already in the Bin changes nothing and returns the same body, which is why the SDK retries it. Scopes: `threads:write`. **Parameters** - `id` (`String`, required): Thread id. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `object` set to `thread`, `id` and `trashed` set to true. **Example** ```java Map result = client.threads().trash("CAHk7pQ2x9LmZ4-mail.example.com"); System.out.println(result.get("id") + " " + result.get("trashed")); ``` **Notes** - `restore` takes a thread back out of the Bin. `update` refuses `TRASH` in `removeLabelIds` as well as in `addLabelIds`. - Trashing a snoozed thread also cancels its scheduled wake, so it does not reappear in the inbox later. - A thread delivered to no address the key covers is a 404. Also available in: API [`POST /threads/{id}/trash`](https://openemail.uk/docs/api/reference/threads#post-threads-id-trash); TypeScript [`threads.trash()`](https://openemail.uk/docs/sdk/reference/threads#trash); Python [`threads.trash()`](https://openemail.uk/docs/python/reference/threads#trash); Ruby [`threads.trash`](https://openemail.uk/docs/ruby/reference/threads#trash); PHP [`threads->trash`](https://openemail.uk/docs/php/reference/threads#trash); Go [`Threads.Trash`](https://openemail.uk/docs/go/reference/threads#trash); C# [`Threads.TrashAsync`](https://openemail.uk/docs/csharp/reference/threads#trash); CLI [`openemail threads trash`](https://openemail.uk/docs/cli/reference/threads#threads-trash). ### `threads().snooze` Hide a thread until a set time ```java Map snooze(String id, String wakeAt, RequestOptions options) ``` Adds `SNOOZED`, removes `INBOX` and stores a wake time, all in one call. Both halves matter: the label hides the thread and the stored wake time is what brings it back. A thread labelled `SNOOZED` any other way would never return, which is why `update` refuses that label. `wakeAt` takes an `Instant` or an ISO 8601 string. The SDK sends an `Instant` as an ISO 8601 instant in UTC, and the server answers 422 `invalid_parameter` on `wakeAt` when the value does not parse or is not in the future. Snoozing a thread that is already snoozed replaces its wake time. Threads are woken by an hourly sweep, so one comes back at the first sweep after `wakeAt`, up to about an hour late. Opening the Snoozed folder in the app wakes overdue threads straight away. A thread always wakes into the inbox. Scopes: `threads:write`. **Parameters** - `id` (`String`, required): Thread id. - `wakeAt` (`Instant or String`, required): When the thread should return, a future instant. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `id` and `snoozedUntil`, the wake time normalised to a UTC ISO 8601 string. **Example** ```java Map snoozed = client.threads().snooze("CAHk7pQ2x9LmZ4-mail.example.com", "2026-10-11T09:00:00.000Z"); System.out.println(snoozed.get("snoozedUntil")); ``` **Notes** - Only `INBOX` is removed, so a thread snoozed from another folder keeps that folder's label while it sleeps and wakes carrying both. - A string with no zone offset is read in the server's local zone, so send `Z` or an explicit offset. - The SDK retries this call, which is safe because a repeat stores the same wake time. Also available in: API [`POST /threads/{id}/snooze`](https://openemail.uk/docs/api/reference/threads#post-threads-id-snooze); TypeScript [`threads.snooze()`](https://openemail.uk/docs/sdk/reference/threads#snooze); Python [`threads.snooze()`](https://openemail.uk/docs/python/reference/threads#snooze); Ruby [`threads.snooze`](https://openemail.uk/docs/ruby/reference/threads#snooze); PHP [`threads->snooze`](https://openemail.uk/docs/php/reference/threads#snooze); Go [`Threads.Snooze`](https://openemail.uk/docs/go/reference/threads#snooze); C# [`Threads.SnoozeAsync`](https://openemail.uk/docs/csharp/reference/threads#snooze); CLI [`openemail threads snooze`](https://openemail.uk/docs/cli/reference/threads#threads-snooze). ### `threads().unsnooze` Bring a snoozed thread back now ```java Map unsnooze(String id, RequestOptions options) ``` Adds `INBOX`, removes `SNOOZED` and deletes the stored wake time, so the thread returns immediately and the hourly sweep leaves it alone afterwards. A thread that is not snoozed is left where it is, so an archived thread stays archived, and the response still reports `snoozedUntil` as null. Scopes: `threads:write`. **Parameters** - `id` (`String`, required): Thread id. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `id` and `snoozedUntil` set to null. **Example** ```java Map result = client.threads().unsnooze("CAHk7pQ2x9LmZ4-mail.example.com"); System.out.println(result.get("snoozedUntil")); ``` **Notes** - Removing `SNOOZED` through `update` is refused with 422 `label_not_directly_settable`, because it would leave the wake time scheduled. - Safe to retry, and the SDK does: a second call applies the same labels and deletes a wake time that is already gone. Also available in: API [`POST /threads/{id}/unsnooze`](https://openemail.uk/docs/api/reference/threads#post-threads-id-unsnooze); TypeScript [`threads.unsnooze()`](https://openemail.uk/docs/sdk/reference/threads#unsnooze); Python [`threads.unsnooze()`](https://openemail.uk/docs/python/reference/threads#unsnooze); Ruby [`threads.unsnooze`](https://openemail.uk/docs/ruby/reference/threads#unsnooze); PHP [`threads->unsnooze`](https://openemail.uk/docs/php/reference/threads#unsnooze); Go [`Threads.Unsnooze`](https://openemail.uk/docs/go/reference/threads#unsnooze); C# [`Threads.UnsnoozeAsync`](https://openemail.uk/docs/csharp/reference/threads#unsnooze); CLI [`openemail threads unsnooze`](https://openemail.uk/docs/cli/reference/threads#threads-unsnooze). ### `threads().mute` Mute a thread ```java Map mute(String id, RequestOptions options) ``` Mutes a conversation, as Mute does in the app. A thread in the inbox moves to the archive, and from then on new mail in it goes straight to the archive, unread, with no push, sound or desktop notice. A webhook for that mail carries `muted` set to true. Thread state belongs to the whole workspace, so the thread is muted for everyone on it, and mail addressed only to you does not bring it back. Calling it again changes nothing, which is why the SDK retries it. `update` with `MUTE` in `addLabelIds` does the same. Scopes: `threads:write`. **Parameters** - `id` (`String`, required): Thread id. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `object` set to `thread`, `id` and `muted` set to true. **Example** ```java Map muted = client.threads().mute("CAHk7pQ2x9LmZ4-mail.example.com"); System.out.println(muted.get("id") + " " + muted.get("muted")); ``` **Notes** - Only a thread in the inbox moves. One in Sent, the archive or Snoozed stays where it is. - A muted thread carries the built-in `MUTE` label, which `get` shows among its labels and `is:muted` finds in `query`. - `unmute` takes the mute off. A thread delivered to no address the key covers is a 404. Also available in: API [`POST /threads/{id}/mute`](https://openemail.uk/docs/api/reference/threads#post-threads-id-mute); TypeScript [`threads.mute()`](https://openemail.uk/docs/sdk/reference/threads#mute); Python [`threads.mute()`](https://openemail.uk/docs/python/reference/threads#mute); Ruby [`threads.mute`](https://openemail.uk/docs/ruby/reference/threads#mute); PHP [`threads->mute`](https://openemail.uk/docs/php/reference/threads#mute); Go [`Threads.Mute`](https://openemail.uk/docs/go/reference/threads#mute); C# [`Threads.MuteAsync`](https://openemail.uk/docs/csharp/reference/threads#mute); CLI [`openemail threads mute`](https://openemail.uk/docs/cli/reference/threads#threads-mute). ### `threads().unmute` Take the mute off a thread ```java Map unmute(String id, RequestOptions options) ``` Takes the mute off, so the next message in the thread arrives in the inbox and alerts people again. The thread stays where it is. Move it back with `update` and `INBOX` in `addLabelIds` if you want it in the inbox now. A thread that is not muted is left as it is, which is why the SDK retries this call. Scopes: `threads:write`. **Parameters** - `id` (`String`, required): Thread id. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `object` set to `thread`, `id` and `muted` set to false. **Example** ```java Map result = client.threads().unmute("CAHk7pQ2x9LmZ4-mail.example.com"); System.out.println(result.get("muted")); ``` **Notes** - Unmuting is for the whole workspace, as muting is: the thread alerts everyone on it again. - A thread delivered to no address the key covers is a 404. Also available in: API [`POST /threads/{id}/unmute`](https://openemail.uk/docs/api/reference/threads#post-threads-id-unmute); TypeScript [`threads.unmute()`](https://openemail.uk/docs/sdk/reference/threads#unmute); Python [`threads.unmute()`](https://openemail.uk/docs/python/reference/threads#unmute); Ruby [`threads.unmute`](https://openemail.uk/docs/ruby/reference/threads#unmute); PHP [`threads->unmute`](https://openemail.uk/docs/php/reference/threads#unmute); Go [`Threads.Unmute`](https://openemail.uk/docs/go/reference/threads#unmute); C# [`Threads.UnmuteAsync`](https://openemail.uk/docs/csharp/reference/threads#unmute); CLI [`openemail threads unmute`](https://openemail.uk/docs/cli/reference/threads#threads-unmute). ### `threads().listAttachments` List a message's attachments with their content ```java List> listAttachments(String id, String messageId, RequestOptions options) ``` Returns the attachments of one message with each file's bytes inlined as base64 in `content`. The thread is checked first and then the message, so a `messageId` that is not on that thread is a 404 even when it exists elsewhere in the mailbox. Take message ids from the `messages` of `threads().get`. This is the display list. The ciphertext of an encrypted envelope is in it and downloads like any other file, named `encrypted-message.asc` when it arrived without a name. The PGP/MIME version part and any detached signature are held out on purpose. Every part keeps its id in the message's `encryption.parts`, and for those two the id is a correlation key only: no route returns their bytes. Every file comes back whole in a single response, with no size cap and no range reads, so a message carrying large files makes a large response. Scopes: `threads:read`. **Parameters** - `id` (`String`, required): Thread id the message belongs to. - `messageId` (`String`, required): Message id from that thread's `messages`. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A list of maps, each with `attachmentId`, `filename`, `contentType`, `size` and base64 `content`. **Example** ```java Map thread = client.threads().get("CAHk7pQ2x9LmZ4-mail.example.com"); List> files = client.threads().listAttachments((String) thread.get("id"), "undefined"); for (Map attachment : files) { System.out.println(attachment.get("object") + " " + attachment.get("attachmentId")); } ``` **Notes** - When the stored bytes for a file cannot be found, `content` is an empty string rather than null, so check its length before decoding. - Both ids must match: a real message id paired with the wrong thread id is a 404 `resource_not_found`. - A thread delivered to no address the key covers is a 404 before the message is looked at. Also available in: API [`GET /threads/{id}/messages/{messageId}/attachments`](https://openemail.uk/docs/api/reference/threads#get-threads-id-messages-messageid-attachments); TypeScript [`threads.listAttachments()`](https://openemail.uk/docs/sdk/reference/threads#listAttachments); Python [`threads.list_attachments()`](https://openemail.uk/docs/python/reference/threads#listAttachments); Ruby [`threads.list_attachments`](https://openemail.uk/docs/ruby/reference/threads#listAttachments); PHP [`threads->listAttachments`](https://openemail.uk/docs/php/reference/threads#listAttachments); Go [`Threads.ListAttachments`](https://openemail.uk/docs/go/reference/threads#listAttachments); C# [`Threads.ListAttachmentsAsync`](https://openemail.uk/docs/csharp/reference/threads#listAttachments); CLI [`openemail threads list-attachments`](https://openemail.uk/docs/cli/reference/threads#threads-list-attachments). ### `threads().listNotes` List the notes on a thread ```java List> listNotes(String id, RequestOptions options) ``` Returns every note on one thread, the Notes panel of the reading pane: pinned notes first, then the rest in the order they were arranged. Notes are private to a person. A key reads and writes the notes of the workspace owner, and an app those of the person who connected it. A key limited to particular addresses reaches only the notes on threads that arrived at them. Scopes: `threads:read`. **Parameters** - `id` (`String`, required): Thread id. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A list of maps, each with `id`, `threadId`, `content`, `color`, `pinned`, `order`, `createdAt` and `updatedAt`. **Example** ```java List> notes = client.threads().listNotes("CAHk7pQ2x9LmZ4-mail.example.com"); for (Map note : notes) { System.out.println(note.get("pinned") + " " + note.get("content")); } ``` **Notes** - A thread delivered to no address the key covers is a 404. Also available in: API [`GET /threads/{id}/notes`](https://openemail.uk/docs/api/reference/notes#get-threads-id-notes); TypeScript [`threads.listNotes()`](https://openemail.uk/docs/sdk/reference/threads#listNotes); Python [`threads.list_notes()`](https://openemail.uk/docs/python/reference/threads#listNotes); Ruby [`threads.list_notes`](https://openemail.uk/docs/ruby/reference/threads#listNotes); PHP [`threads->listNotes`](https://openemail.uk/docs/php/reference/threads#listNotes); Go [`Threads.ListNotes`](https://openemail.uk/docs/go/reference/threads#listNotes); C# [`Threads.ListNotesAsync`](https://openemail.uk/docs/csharp/reference/threads#listNotes); CLI [`openemail threads list-notes`](https://openemail.uk/docs/cli/reference/threads#threads-list-notes). ### `threads().createNote` Add a note to a thread ```java Map createNote(String id, Map body, RequestOptions options) ``` Pins a private note to a thread, as the Notes panel does. A new note goes after the others, and `pinned` keeps it at the top. Notes are private to a person. A key reads and writes the notes of the workspace owner, and an app those of the person who connected it. A key limited to particular addresses reaches only the notes on threads that arrived at them. Scopes: `threads:write`. **Parameters** - `id` (`String`, required): Thread id. - `body.content` (`String`, required): The text of the note, up to 20,000 characters. Leading and trailing spaces are trimmed. - `body.color` (`String`): One of the eight the app offers: `default`, `red`, `orange`, `yellow`, `green`, `blue`, `purple` or `pink`, as in `uk.openemail.constants.ThreadNoteColors`. Defaults to `default`. - `body.pinned` (`boolean`): Keeps the note above the others. Defaults to false. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map for the new note, with the fields `listNotes` returns. **Example** ```java Map note = client.threads().createNote("CAHk7pQ2x9LmZ4-mail.example.com", Body.of( "content", "Waiting on the signed contract before replying.", "color", "yellow", "pinned", true )); System.out.println(note.get("id")); ``` **Notes** - The SDK does not retry it, because a second call would add a second note. Also available in: API [`POST /threads/{id}/notes`](https://openemail.uk/docs/api/reference/notes#post-threads-id-notes); TypeScript [`threads.createNote()`](https://openemail.uk/docs/sdk/reference/threads#createNote); Python [`threads.create_note()`](https://openemail.uk/docs/python/reference/threads#createNote); Ruby [`threads.create_note`](https://openemail.uk/docs/ruby/reference/threads#createNote); PHP [`threads->createNote`](https://openemail.uk/docs/php/reference/threads#createNote); Go [`Threads.CreateNote`](https://openemail.uk/docs/go/reference/threads#createNote); C# [`Threads.CreateNoteAsync`](https://openemail.uk/docs/csharp/reference/threads#createNote); CLI [`openemail threads create-note`](https://openemail.uk/docs/cli/reference/threads#threads-create-note). ### `threads().updateNote` Change a note ```java Map updateNote(String id, String noteId, Map patch, RequestOptions options) ``` Changes the text of a note, its colour or whether it is pinned. Give at least one of the three. A note id that is not on this thread is a 404, even when the note exists on another thread. Scopes: `threads:write`. **Parameters** - `id` (`String`, required): Thread id. - `noteId` (`String`, required): The note's id, from `listNotes`. - `patch.content` (`String`): The new text, up to 20,000 characters. - `patch.color` (`String`): The new colour, one of `uk.openemail.constants.ThreadNoteColors`. - `patch.pinned` (`boolean`): Pins or unpins it. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map for the note as it is now, with the fields `listNotes` returns. **Example** ```java Map note = client.threads().updateNote("CAHk7pQ2x9LmZ4-mail.example.com", "b3d1f0c2-7a4e-4f7b-9c1d-2e8f6a5b4c3d", Body.of("pinned", false)); System.out.println(note.get("pinned")); ``` **Notes** - Safe to repeat: setting the same values twice leaves the note as it was. Also available in: API [`PATCH /threads/{id}/notes/{noteId}`](https://openemail.uk/docs/api/reference/notes#patch-threads-id-notes-noteid); TypeScript [`threads.updateNote()`](https://openemail.uk/docs/sdk/reference/threads#updateNote); Python [`threads.update_note()`](https://openemail.uk/docs/python/reference/threads#updateNote); Ruby [`threads.update_note`](https://openemail.uk/docs/ruby/reference/threads#updateNote); PHP [`threads->updateNote`](https://openemail.uk/docs/php/reference/threads#updateNote); Go [`Threads.UpdateNote`](https://openemail.uk/docs/go/reference/threads#updateNote); C# [`Threads.UpdateNoteAsync`](https://openemail.uk/docs/csharp/reference/threads#updateNote); CLI [`openemail threads update-note`](https://openemail.uk/docs/cli/reference/threads#threads-update-note). ### `threads().deleteNote` Delete a note ```java Map deleteNote(String id, String noteId, RequestOptions options) ``` Deletes a note for good. There is no bin for notes. Scopes: `threads:write`. **Parameters** - `id` (`String`, required): Thread id. - `noteId` (`String`, required): The note's id, from `listNotes`. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `object` set to `note`, `id`, `threadId` and `deleted` set to true. **Example** ```java Map result = client.threads().deleteNote("CAHk7pQ2x9LmZ4-mail.example.com", "b3d1f0c2-7a4e-4f7b-9c1d-2e8f6a5b4c3d"); System.out.println(result.get("id")); ``` **Notes** - The SDK does not retry a delete. A 404 on your own second attempt after a lost response means the first one worked. Also available in: API [`DELETE /threads/{id}/notes/{noteId}`](https://openemail.uk/docs/api/reference/notes#delete-threads-id-notes-noteid); TypeScript [`threads.deleteNote()`](https://openemail.uk/docs/sdk/reference/threads#deleteNote); Python [`threads.delete_note()`](https://openemail.uk/docs/python/reference/threads#deleteNote); Ruby [`threads.delete_note`](https://openemail.uk/docs/ruby/reference/threads#deleteNote); PHP [`threads->deleteNote`](https://openemail.uk/docs/php/reference/threads#deleteNote); Go [`Threads.DeleteNote`](https://openemail.uk/docs/go/reference/threads#deleteNote); C# [`Threads.DeleteNoteAsync`](https://openemail.uk/docs/csharp/reference/threads#deleteNote); CLI [`openemail threads delete-note`](https://openemail.uk/docs/cli/reference/threads#threads-delete-note). ### `threads().reorderNotes` Arrange the notes on a thread ```java List> reorderNotes(String id, List ids, RequestOptions options) ``` Sets the order of every note on a thread at once, first to last, as dragging them in the Notes panel does. Pinned notes still come first. `ids` has to name every note on the thread exactly once. Anything else is a 422 `invalid_parameter` on `ids`, and nothing moves. Scopes: `threads:write`. **Parameters** - `id` (`String`, required): Thread id. - `ids` (`List`, required): Every note id on the thread, in the order you want them. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A list of note maps in the new order. **Example** ```java List> notes = client.threads().listNotes("CAHk7pQ2x9LmZ4-mail.example.com"); List> items = client.threads().reorderNotes("CAHk7pQ2x9LmZ4-mail.example.com", List.of((String) notes.get(0).get("id"))); for (Map thread : items) { System.out.println(thread.get("id") + " " + thread.get("createdAt")); } ``` **Notes** - Safe to repeat: the same order twice leaves the notes as they were. Also available in: API [`POST /threads/{id}/notes/reorder`](https://openemail.uk/docs/api/reference/notes#post-threads-id-notes-reorder); TypeScript [`threads.reorderNotes()`](https://openemail.uk/docs/sdk/reference/threads#reorderNotes); Python [`threads.reorder_notes()`](https://openemail.uk/docs/python/reference/threads#reorderNotes); Ruby [`threads.reorder_notes`](https://openemail.uk/docs/ruby/reference/threads#reorderNotes); PHP [`threads->reorderNotes`](https://openemail.uk/docs/php/reference/threads#reorderNotes); Go [`Threads.ReorderNotes`](https://openemail.uk/docs/go/reference/threads#reorderNotes); C# [`Threads.ReorderNotesAsync`](https://openemail.uk/docs/csharp/reference/threads#reorderNotes); CLI [`openemail threads reorder-notes`](https://openemail.uk/docs/cli/reference/threads#threads-reorder-notes). ### `threads().counts` Count the mail in each folder ```java Map counts(RequestOptions options) ``` Returns what the sidebar of the app shows: how many conversations each folder holds and how many of them are unread, how many drafts are waiting, how many conversations each of your labels has in each folder, how many inbox conversations sit in each inbox tab, and how many inbox conversations arrived at each address of the workspace. `folders` has one row per folder, named by its label id in lower case: `inbox`, `sent`, `spam`, `archive`, `trash` and `snoozed`, then `draft`, whose `count` is the drafts waiting to be sent and whose `unread` is always 0, then `unread`, whose `count` is the unread conversations in the inbox. `labels` has one row for each of your labels and each folder it has conversations in, with `id`, `folder`, `count` and `unread`, so a label with nothing in a folder has no row for it. `categories` has one row for each inbox tab, with `category`, `count` and `unread`, counting inbox conversations only: `primary`, `promotions`, `updates`, `social` and `forums`, where `primary` is everything not sorted into another tab. `addresses` counts the inbox per address the mail was delivered to, with `null` for mail that recorded none. A key limited to particular addresses counts only the mail that arrived at them and the drafts written from them. `address` narrows every count to one address, and one the key does not reach counts nothing rather than failing. Scopes: `threads:read`. **Parameters** - `options.address` (`String`): Count only the mail delivered to this address. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `object` set to `mailbox_counts`, `folders`, `addresses`, `labels` and `categories`. Each folder is a map with `label`, `count` and `unread`, each address a map with `address` and `count`, each label a map with `id`, `folder`, `count` and `unread`, and each category a map with `category`, `count` and `unread`. **Example** ```java Map counts = client.threads().counts(); System.out.println(counts.get("folders") + " " + counts.get("addresses") + " " + counts.get("labels")); ``` **Notes** - Read only, so the SDK retries it after a network failure like any other read. Also available in: API [`GET /threads/counts`](https://openemail.uk/docs/api/reference/threads#get-threads-counts); TypeScript [`threads.counts()`](https://openemail.uk/docs/sdk/reference/threads#counts); Python [`threads.counts()`](https://openemail.uk/docs/python/reference/threads#counts); Ruby [`threads.counts`](https://openemail.uk/docs/ruby/reference/threads#counts); PHP [`threads->counts`](https://openemail.uk/docs/php/reference/threads#counts); Go [`Threads.Counts`](https://openemail.uk/docs/go/reference/threads#counts); C# [`Threads.CountsAsync`](https://openemail.uk/docs/csharp/reference/threads#counts); CLI [`openemail threads counts`](https://openemail.uk/docs/cli/reference/threads#threads-counts). ### `threads().summary` Read the summary of a thread ```java Map summary(String id, RequestOptions options) ``` Returns the short AI summary the reading pane shows above a thread. A summary is written the first time it is asked for and then kept, and the first request after a newer message arrives writes it again, so reading one is cheap. `state` is `ready` with the text in `summary`, `pending` while the first one is being written, or `none` when there is nothing to summarise, such as a thread holding a message that arrived encrypted, whose body OpenEmail never reads. While a newer summary is being written, the one before it comes back as `ready`. A `pending` answer starts the writing, so ask again a few seconds later. Scopes: `threads:read`. **Parameters** - `id` (`String`, required): Thread id. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `object` set to `thread_summary`, `threadId`, `state` and `summary`, with `summary` null unless `state` is `ready`. **Example** ```java Map result = client.threads().summary("CAHk7pQ2x9LmZ4-mail.example.com"); System.out.println(result.get("state") + " " + result.get("summary")); ``` **Notes** - Summaries spend no AI actions, whether one is written or only read. - A thread delivered to no address the key covers is a 404. Also available in: API [`GET /threads/{id}/summary`](https://openemail.uk/docs/api/reference/threads#get-threads-id-summary); TypeScript [`threads.summary()`](https://openemail.uk/docs/sdk/reference/threads#summary); Python [`threads.summary()`](https://openemail.uk/docs/python/reference/threads#summary); Ruby [`threads.summary`](https://openemail.uk/docs/ruby/reference/threads#summary); PHP [`threads->summary`](https://openemail.uk/docs/php/reference/threads#summary); Go [`Threads.Summary`](https://openemail.uk/docs/go/reference/threads#summary); C# [`Threads.SummaryAsync`](https://openemail.uk/docs/csharp/reference/threads#summary); CLI [`openemail threads summary`](https://openemail.uk/docs/cli/reference/threads#threads-summary). ### `threads().replySuggestions` Suggest replies to a thread ```java Map replySuggestions(String id, RequestOptions options) ``` Returns up to three short replies to the latest message of the thread, the ones the reading pane offers under it. Each has a `label`, a few words that say what it answers, and a `body`, the reply itself in plain text, ready to send with `emails().send` or to keep with `drafts().create`. They are written in the language of that message and the voice of the mail this workspace sends, from the conversation, what was written to this correspondent before, what is known about their organisation and, when the message asks for a time, the busy times of the calendar. Suggestions are written once for each new message and kept, so asking again is free until another message arrives. `state` is `ready` with the suggestions, `pending` while they are being written, so ask again a few seconds later, or `none` when the message needs no reply: your own reply came last, or it is a newsletter, an automated notice, mail from a no-reply address, spam or an encrypted message. Every thread is `none` in a workspace that turned `replySuggestions` off with `settings().update`. `sources` names the knowledge base items the suggestions drew on: the pinned notes at the levels of the receiving address and the items whose passages matched the message, each with `id`, `title`, `kind`, `scope` and `url`. It is empty when none were used. Scopes: `threads:read`. **Parameters** - `id` (`String`, required): Thread id. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `object` set to `reply_suggestions`, `threadId`, `messageId`, `state`, `suggestions` and `sources`, with `messageId` naming the message they answer, `suggestions` empty unless `state` is `ready` and `sources` the knowledge base items they drew on. Each suggestion is a map with `label` and `body`. **Example** ```java Map result = client.threads().replySuggestions("CAHk7pQ2x9LmZ4-mail.example.com"); System.out.println(result.get("state") + " " + result.get("suggestions")); ``` **Notes** - Writing suggestions spends none of the workspace's AI actions. A workspace has suggestions written for a limited number of new messages a day, and past it a thread reads `none` until the next day. - A thread delivered to no address the key covers is a 404. - A server without AI answers 409 `ai_not_configured`. Also available in: API [`GET /threads/{id}/reply-suggestions`](https://openemail.uk/docs/api/reference/threads#get-threads-id-reply-suggestions); TypeScript [`threads.replySuggestions()`](https://openemail.uk/docs/sdk/reference/threads#replySuggestions); Python [`threads.reply_suggestions()`](https://openemail.uk/docs/python/reference/threads#replySuggestions); Ruby [`threads.reply_suggestions`](https://openemail.uk/docs/ruby/reference/threads#replySuggestions); PHP [`threads->replySuggestions`](https://openemail.uk/docs/php/reference/threads#replySuggestions); Go [`Threads.ReplySuggestions`](https://openemail.uk/docs/go/reference/threads#replySuggestions); C# [`Threads.ReplySuggestionsAsync`](https://openemail.uk/docs/csharp/reference/threads#replySuggestions); CLI [`openemail threads reply-suggestions`](https://openemail.uk/docs/cli/reference/threads#threads-reply-suggestions). ### `threads().restore` Take a thread out of the Bin ```java Map restore(String id, RequestOptions options) ``` Puts a thread back in the inbox, out of the Bin and out of Spam, which is what Restore from Bin and Move to inbox do in the app. It is the undo of `trash`. Calling it on a thread that is already in the inbox changes nothing and returns the same body, which is why the SDK retries it. Scopes: `threads:write`. **Parameters** - `id` (`String`, required): Thread id. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `object` set to `thread`, `id` and `restored` set to true. **Example** ```java Map restored = client.threads().restore("CAHk7pQ2x9LmZ4-mail.example.com"); System.out.println(restored.get("restored")); ``` **Notes** - A thread that was archived before it went to the Bin comes back to the inbox, not to the archive. - A thread delivered to no address the key covers is a 404. Also available in: API [`POST /threads/{id}/restore`](https://openemail.uk/docs/api/reference/threads#post-threads-id-restore); TypeScript [`threads.restore()`](https://openemail.uk/docs/sdk/reference/threads#restore); Python [`threads.restore()`](https://openemail.uk/docs/python/reference/threads#restore); Ruby [`threads.restore`](https://openemail.uk/docs/ruby/reference/threads#restore); PHP [`threads->restore`](https://openemail.uk/docs/php/reference/threads#restore); Go [`Threads.Restore`](https://openemail.uk/docs/go/reference/threads#restore); C# [`Threads.RestoreAsync`](https://openemail.uk/docs/csharp/reference/threads#restore); CLI [`openemail threads restore`](https://openemail.uk/docs/cli/reference/threads#threads-restore). ### `threads().delete` Delete a thread for good ```java Map delete(String id, RequestOptions options) ``` Deletes every message in a thread, with its attachments, which is what Delete from Bin does in the app. It cannot be undone. It works on a thread in any folder, so call `trash` instead when you only mean to discard the thread: a trashed thread stays readable and `restore` brings it back. Scopes: `threads:write`. **Parameters** - `id` (`String`, required): Thread id. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `object` set to `thread`, `id` and `deleted` set to true. **Example** ```java Map result = client.threads().delete("CAHk7pQ2x9LmZ4-mail.example.com"); System.out.println(result.get("id")); ``` **Notes** - The SDK does not retry a delete. A 404 on your own second attempt after a lost response means the first one worked. - A 500 `thread_delete_failed` means nothing was removed, so the call is safe to repeat. - A thread delivered to no address the key covers is a 404. Also available in: API [`DELETE /threads/{id}`](https://openemail.uk/docs/api/reference/threads#delete-threads-id); TypeScript [`threads.delete()`](https://openemail.uk/docs/sdk/reference/threads#delete); Python [`threads.delete()`](https://openemail.uk/docs/python/reference/threads#delete); Ruby [`threads.delete`](https://openemail.uk/docs/ruby/reference/threads#delete); PHP [`threads->delete`](https://openemail.uk/docs/php/reference/threads#delete); Go [`Threads.Delete`](https://openemail.uk/docs/go/reference/threads#delete); C# [`Threads.DeleteAsync`](https://openemail.uk/docs/csharp/reference/threads#delete); CLI [`openemail threads delete`](https://openemail.uk/docs/cli/reference/threads#threads-delete). ### `threads().unsubscribe` Unsubscribe from the sender of a thread ```java Map unsubscribe(String id, RequestOptions options) ``` Does what the Unsubscribe button of the reading pane does: finds the subscription behind the newest message of the thread that carries a `List-Unsubscribe` header and unsubscribes from it the way the sender asks for, with a one-click request or an unsubscribe email. A sender that only offers a page cannot be unsubscribed by a program, so `method` is `link` and `url` is the page a person has to open. A thread with no unsubscribe header is a 422 `unsubscribe_unsupported`, and a thread delivered to no address the key covers is a 404. Scopes: `threads:write`. **Parameters** - `id` (`String`, required): Thread id. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `object` set to `unsubscribe`, `threadId`, `subscriptionId`, `method`, `url` and `binned`. **Example** ```java Map result = client.threads().unsubscribe("CAHk7pQ2x9LmZ4-mail.example.com"); System.out.println(result.get("method")); ``` **Notes** - The SDK does not retry it, because a second call can send a second unsubscribe email. Also available in: API [`POST /threads/{id}/unsubscribe`](https://openemail.uk/docs/api/reference/subscriptions#post-threads-id-unsubscribe); TypeScript [`threads.unsubscribe()`](https://openemail.uk/docs/sdk/reference/threads#unsubscribe); Python [`threads.unsubscribe()`](https://openemail.uk/docs/python/reference/threads#unsubscribe); Ruby [`threads.unsubscribe`](https://openemail.uk/docs/ruby/reference/threads#unsubscribe); PHP [`threads->unsubscribe`](https://openemail.uk/docs/php/reference/threads#unsubscribe); Go [`Threads.Unsubscribe`](https://openemail.uk/docs/go/reference/threads#unsubscribe); C# [`Threads.UnsubscribeAsync`](https://openemail.uk/docs/csharp/reference/threads#unsubscribe); CLI [`openemail threads unsubscribe`](https://openemail.uk/docs/cli/reference/threads#threads-unsubscribe). ### `threads().getEvent` Read the event a thread carries ```java Map getEvent(String id, RequestOptions options) ``` Returns the calendar event that came with an invitation in the thread, as the invitation card of the reading pane shows it. Answer it with `calendar().respondToEvent`. Scopes: `calendar:read`. **Parameters** - `id` (`String`, required): Thread id, as `threads().list` returns it. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map, the event as `calendar().getEvent` returns it. **Example** ```java Map event = client.threads().getEvent("thr_6d1a9c4e2b7f30d85e1c4a92"); System.out.println(event.get("summary") + " " + event.get("start")); ``` **Notes** - A thread with no event, or one the key does not reach, is a 404. Also available in: API [`GET /threads/{id}/event`](https://openemail.uk/docs/api/reference/calendar#get-threads-id-event); TypeScript [`threads.getEvent()`](https://openemail.uk/docs/sdk/reference/threads#getEvent); Python [`threads.get_event()`](https://openemail.uk/docs/python/reference/threads#getEvent); Ruby [`threads.get_event`](https://openemail.uk/docs/ruby/reference/threads#getEvent); PHP [`threads->getEvent`](https://openemail.uk/docs/php/reference/threads#getEvent); Go [`Threads.GetEvent`](https://openemail.uk/docs/go/reference/threads#getEvent); C# [`Threads.GetEventAsync`](https://openemail.uk/docs/csharp/reference/threads#getEvent); CLI [`openemail threads get-event`](https://openemail.uk/docs/cli/reference/threads#threads-get-event). ### `threads().listSenderCategories` List the senders that always go to one inbox tab ```java List> listSenderCategories(RequestOptions options) ``` Returns the senders whose mail always goes to one inbox tab, by address. New mail is sorted into Primary, Promotions, Updates, Social or Forums by plain rules, and a choice saved here wins over them. `list` takes `category` to read one tab. The choices belong to the workspace and apply to every address in it. A workspace holds at most 2,000 of them, and they come back as one plain list with no paging. Scopes: `threads:read`. **Parameters** - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A list of maps, each with `object` set to `sender_category`, `sender`, `category` and `updatedAt`. `sender` is in lower case and `category` is the tab their mail goes to. **Example** ```java List> choices = client.threads().listSenderCategories(); for (Map senderCategory : choices) { System.out.println(senderCategory.get("object") + " " + senderCategory.get("sender")); } ``` **Notes** - A key or an app limited to particular addresses or domains can read the choices but not change them. - Read only, so the SDK retries it after a network failure like any other read. Also available in: API [`GET /sender-categories`](https://openemail.uk/docs/api/reference/threads#get-sender-categories); TypeScript [`threads.listSenderCategories()`](https://openemail.uk/docs/sdk/reference/threads#listSenderCategories); Python [`threads.list_sender_categories()`](https://openemail.uk/docs/python/reference/threads#listSenderCategories); Ruby [`threads.list_sender_categories`](https://openemail.uk/docs/ruby/reference/threads#listSenderCategories); PHP [`threads->listSenderCategories`](https://openemail.uk/docs/php/reference/threads#listSenderCategories); Go [`Threads.ListSenderCategories`](https://openemail.uk/docs/go/reference/threads#listSenderCategories); C# [`Threads.ListSenderCategoriesAsync`](https://openemail.uk/docs/csharp/reference/threads#listSenderCategories); CLI [`openemail threads list-sender-categories`](https://openemail.uk/docs/cli/reference/threads#threads-list-sender-categories). ### `threads().setSenderCategory` Always sort a sender into one inbox tab ```java Map setSenderCategory(String email, String category, RequestOptions options) ``` Saves the tab for one sender and moves the inbox threads whose newest message is from them, up to the newest 1,000, into it. Mail from them is sorted there from now on, whatever the rules would say. Saving again replaces the choice. A workspace holds at most 2,000 choices, and the call past that is a 422 `sender_category_limit_reached`. They apply to every address in the workspace, so a key or an app limited to particular addresses or domains can read them but not change them, and gets a 422 `capability_unsupported`. Scopes: `threads:write`. **Parameters** - `email` (`String`, required): The address of the sender, compared without case. - `category` (`String`, required): The inbox tab their mail goes to: `primary`, `promotions`, `updates`, `social` or `forums`, as in `uk.openemail.constants.InboxCategories`. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `object` set to `sender_category`, `sender`, `category` and `updatedAt`, with `sender` in lower case. **Example** ```java Map choice = client.threads().setSenderCategory("news@example.com", "promotions"); System.out.println(choice.get("sender") + " " + choice.get("category") + " " + choice.get("updatedAt")); ``` **Notes** - An address or a category that is not valid is a 422 `invalid_parameter`. - Choosing `primary` keeps a sender out of the other tabs, which is how to stop a newsletter you read from being sorted away. - The SDK retries this call after a network failure, which is safe because saving the same choice twice leaves the same choice. Also available in: API [`PUT /sender-categories/{email}`](https://openemail.uk/docs/api/reference/threads#put-sender-categories-email); TypeScript [`threads.setSenderCategory()`](https://openemail.uk/docs/sdk/reference/threads#setSenderCategory); Python [`threads.set_sender_category()`](https://openemail.uk/docs/python/reference/threads#setSenderCategory); Ruby [`threads.set_sender_category`](https://openemail.uk/docs/ruby/reference/threads#setSenderCategory); PHP [`threads->setSenderCategory`](https://openemail.uk/docs/php/reference/threads#setSenderCategory); Go [`Threads.SetSenderCategory`](https://openemail.uk/docs/go/reference/threads#setSenderCategory); C# [`Threads.SetSenderCategoryAsync`](https://openemail.uk/docs/csharp/reference/threads#setSenderCategory); CLI [`openemail threads set-sender-category`](https://openemail.uk/docs/cli/reference/threads#threads-set-sender-category). ### `threads().clearSenderCategory` Remove the tab chosen for a sender ```java Map clearSenderCategory(String email, RequestOptions options) ``` Removes the choice, so new mail from the sender is sorted by the rules again. Threads already sorted stay where they are. Scopes: `threads:write`. **Parameters** - `email` (`String`, required): The address of the sender, compared without case. - `options.apiKey` (`String`): Overrides the client's API key for this call only. **Returns** A map with `object` set to `sender_category`, `sender` and `deleted` set to true, with `sender` in lower case. **Example** ```java Map removed = client.threads().clearSenderCategory("news@example.com"); System.out.println(removed.get("sender") + " " + removed.get("deleted")); ``` **Notes** - A sender with no saved choice is a 404. The SDK does not retry a delete, so a 404 on your own second attempt after a lost response means the first one worked. - A key or an app limited to particular addresses or domains cannot change the choices, and gets a 422 `capability_unsupported`. Also available in: API [`DELETE /sender-categories/{email}`](https://openemail.uk/docs/api/reference/threads#delete-sender-categories-email); TypeScript [`threads.clearSenderCategory()`](https://openemail.uk/docs/sdk/reference/threads#clearSenderCategory); Python [`threads.clear_sender_category()`](https://openemail.uk/docs/python/reference/threads#clearSenderCategory); Ruby [`threads.clear_sender_category`](https://openemail.uk/docs/ruby/reference/threads#clearSenderCategory); PHP [`threads->clearSenderCategory`](https://openemail.uk/docs/php/reference/threads#clearSenderCategory); Go [`Threads.ClearSenderCategory`](https://openemail.uk/docs/go/reference/threads#clearSenderCategory); C# [`Threads.ClearSenderCategoryAsync`](https://openemail.uk/docs/csharp/reference/threads#clearSenderCategory); CLI [`openemail threads clear-sender-category`](https://openemail.uk/docs/cli/reference/threads#threads-clear-sender-category).