Every message Inboundr receives is stored as an email and grouped into a thread. This is what lets an agent read a whole conversation in context instead of one message at a time.

​
The email object

Inbound mail is parsed into clean JSON: sender and recipients, subject, text and HTML bodies, attachment metadata, authentication verdicts, and threading headers. Object keys are prefixed by type — emails are em_…, threads are thr_….
List and thread responses return summaries (no textBody/htmlBody) for speed. Fetch a single email by id to get the full bodies and attachment metadata.

​
Authentication verdicts

Each inbound email carries the results of standard email authentication checks, so you can decide how much to trust it: PASS / FAIL are the meaningful outcomes.

​
Threading

Inboundr groups messages into a threadId using the standard RFC 5322 Message-ID, In-Reply-To, and References headers, so a whole exchange comes back as one conversation via GET /v1/threads/{id} or the get_thread MCP tool — no reassembly required on your end.

​
Attachments

Attachment metadata (filename, content type, size) is always returned. Attachments with stored: true can be downloaded via a short-lived presigned URL — see the attachments endpoint or the get_attachment MCP tool.

​
Reading email

Emails API

List with filters and pagination, or fetch one in full.

Threads API

Fetch every message in a conversation, oldest first.