Concepts & guides
Inbound email, explained.
Receiving email in software is harder than sending it. These are plain-English guides to the ideas behind it — what the terms mean, why the hard parts are hard, and how to go from “an email arrived” to a clean event your app can act on. No mail-server knowledge assumed.
What is inbound email parsing?
Turning a raw received email (MIME) into structured fields — sender, subject, the clean message, attachments — that software can use. What it means, why raw email is messy, and what “clean” parsing adds. Read →
How to receive email as a webhook
The step-by-step path to getting inbound email delivered to your app as an HTTP POST instead of polling a mailbox — including how to verify the request really came from your provider. Read →
What is email intent detection?
Classifying what a reply means — confirm, decline, question, unsubscribe — so a plain-English human reply becomes a decision your code can branch on. Read →
See it in one place
The full reference collects every definition, the payload shape, and the whole API on one page. Or skip the theory: try the live demo — paste a messy reply and watch the clean JSON appear.