Inbound email
Receive email, parsed to clean JSON.
Point an address at Mailhuset and every message that arrives is parsed and posted to your webhook as structured JSON, signed so you know it is real. No mailbox to poll, no MIME to untangle.
X-Mailhuset-Signature: t=1718...,v1=3ba7...
{
"from": "amara@example.com",
"to": "support@yourapp.com",
"subject": "Where is my order?",
"text": "Hi, order #4182 hasn't...",
"attachments": 1,
"message_id": "in_7c2a90"
}Turn a mailbox into an API
Support replies, ticket creation and reply-by-email all start with receiving mail cleanly. Mailhuset does the parsing so your app gets a tidy payload.
Address routing
Route a whole domain or specific addresses to different endpoints, so support and billing mail land where they belong.
Parsed to JSON
Sender, recipients, subject, text and HTML bodies arrive as fields, so you never parse raw MIME yourself.
Attachments handled
Attachments are extracted and made available with the message, rather than left encoded in the body.
Signed and spam-checked
Each inbound webhook is signed, and spam signals are surfaced so you can drop junk before it reaches your app.
Reply threading
Message and thread ids let you tie a reply back to the original conversation without guessing.
One dashboard
Inbound mail shows up in the same activity log as everything else you send, so it is all in one place.
Common questions
- What do I need to receive inbound mail?
- Point an address or subdomain at Mailhuset with a DNS record, set your webhook URL, and inbound messages start arriving as JSON.
- How do I know a webhook really came from Mailhuset?
- Every inbound webhook is signed. Verify the signature with your key before you act on the payload.
- Can I route different addresses to different endpoints?
- Yes. You can send a whole domain to one endpoint or route specific addresses separately.
Let your users reply by email
Point an address at Mailhuset and receive your first parsed message on your webhook in minutes.