Threads

The API pages threads with a pageToken. The client hands it to you as nextCursor and takes it back as cursor, like every other list, and listAll and iterate follow it for you. It is opaque: pass back what you were given and never build one.

sort, dateFrom, dateTo and fromContacts are the thread list’s own controls. sort is newest, oldest, sender or subject, the dates take a Date or an ISO 8601 string and both ends are included, and fromContacts keeps mail whose newest message came from a saved contact. Every order pages to the end without skipping or repeating a thread. With semantic: true the plain words of query match by meaning instead, best match first, and sort does not apply.

addLabelIds takes ids from labels.list and the system ids such as ARCHIVE and STARRED. An id that names no label is refused with a 422 label_not_found rather than created, so make the label with labels.create first. threads.list({ folder: 'USER_DONE' }) lists every thread carrying a label, whichever folder it is in.

content is base64, and an empty string when the stored bytes could not be found, so check its length before decoding. The ciphertext of an encrypted message IS in this list and downloads like any other file; the PGP/MIME version part and any detached signature are not. They keep their ids in encryption.parts and nothing more.

Branch with isSealed, never on the presence of the field. Two of the five formats, pgp-signed and smime-signed, describe a body that arrived in the CLEAR beside a detached signature, so gating on presence hides mail nobody needed to hide, and the user cannot see it or explain it. isSealed ships for exactly that reason: the server states the sealed set once, and a third copy written out of the union is the copy that drifts.

Absence is not plaintext. encryption is missing on every message stored before detection shipped, and on anything that reached the mailbox by a path where the detector never ran. It records that nobody looked, a fact about our coverage rather than about the mail, and nothing backfills it.

setSenderCategory saves the inbox tab for one sender and moves their inbox threads into it, listSenderCategories resolves the saved choices as a plain array, and clearSenderCategory hands the sender back to the sorting rules. A workspace holds at most 2,000 choices, and the call past that is a 422 sender_category_limit_reached.

A thread holds one waiting reminder per person, so setting another, or sending again into the thread with followUpAt, replaces the one that was waiting. A reminder whose thread sits in the Bin or in Spam when it comes due is cancelled. followUps.list resolves a plain array, newest first, and takes status, threadId and limit. A time in the past, or more than 365 days out, is a 422 invalid_follow_up.

outOfOffice.list resolves every reply saved in the workspace, or with address exactly one row, which reads enabled: false when that address never saved one. active says whether mail arriving now is answered. outOfOffice.clear removes a reply, and enabled: false on set pauses one and keeps its text. These calls need settings:read and settings:write.