Thread for developers
The permission layer between your app and your users' email. Scoped, revocable, metadata-first.
Thread is the permission layer between your app and your users' email. Your users grant a scoped, revocable connection to their mailbox; you receive signed webhooks when matching mail arrives and read message metadata on their behalf — without ever handling their password, running a full-mailbox OAuth, or storing their mail.
Bodies are never sent by default. You get the sender, subject, labels, and Thread's classification — enough to build receipt parsers, travel assistants, finance tools, and support automations, without the liability of holding raw inboxes.
How it fits together
1 · Connect
Drop in a Connect with Thread button. The user authorizes a scoped grant on Thread's hosted consent page and is redirected back with a one-time code.
2 · Exchange
Your server exchanges the code for an accountId — a stable, per-app
pseudonymous handle for that mailbox.
3 · Receive
When mail matching the grant arrives and is classified, Thread POSTs a signed
email.classified webhook to your endpoint.
4 · Read
Call the gateway with your API key to list message metadata, read threads, fetch labels, and mutate (mark read, label, archive).
Start here
Getting started
Your first successful call in about ten minutes.
Integrate
The full connect → exchange → webhook → read flow, end to end.
Configuration
Scopes, filters, constraints, webhook signing, and key rotation.
Examples & starters
Wanderlog, a runnable end-to-end sample app, plus the SDK allow/deny demo.
Scope catalog
Every category and label your app can request, with example matches.
API reference
Every gateway endpoint, generated from the live service schema.