Introduction

Email-Webhook receives email on your behalf and immediately forwards it to an HTTP endpoint you control — sender, subject, body, and attachments delivered as a JSON payload, just like any other webhook.

No IMAP polling. No MIME parsing. No persistent process to run.

Where to go next

• What is an Email Webhook? — how the model works, what the payload looks like, and when to use it instead of IMAP polling.
• Getting Started — sign up, create your first webhook, and receive a live delivery in five minutes.
• Choosing an HTTP Method — when to use POST vs GET and what changes between them.
• Authenticating Your Endpoint — add a custom header so only email-webhook can call your endpoint.
• Debugging with Message Logs — trace individual deliveries and inspect request details.
• Handling Attachments — decode base64 attachments, upload them to S3, and handle large files safely.
• Privacy and Data Retention — what we store and for how long.

Guides:

• AI and LLM Pipelines — feed incoming email into a prompt and generate an AI-powered response.
• AWS Lambda with SST — deploy a serverless webhook handler to AWS using API Gateway v2 and SST v3.
• Email Webhook vs. IMAP Polling — why a push-based webhook beats polling for most use cases.
• Email Webhook vs. SendGrid Inbound Parse — how the two services compare on setup, payload format, and pricing.
• Email Webhook vs. Postmark Inbound — side-by-side comparison of features, latency, and cost.