Webhooks

Note: Webhooks are a premium feature.

ImprovMX provides webhook functionality, enabling you to send incoming emails as structured JSON data to your servers for custom email forwarding applications.

Configuration via Aliases

You can enable webhooks by entering a URL (beginning with http:// or https://) as a forward destination in the app console.

You can test webhooks with free services like webhook.site or webhook.cool before deploying to production.

Multiple destinations — including both email addresses and webhook URLs — can be specified for a single alias by separating them with commas.

Configuration via Rules Routing

Rules Routing also supports webhook destinations, allowing matching logic (regex, CEL) to determine when webhooks receive emails. Payloads are identical regardless of routing method.

Webhook Payload Structure

Each incoming email triggers a POST request containing JSON with these components:

• Headers — Forwarding service info, SPF records, DKIM signatures, authentication results
• To / From — Recipient and sender details with name and email
• Subject, Message-ID, Date — Email metadata
• Return-Path — Bounce address information
• Timestamp — Unix timestamp of receipt
• Text / HTML — Both plain text and HTML versions of the message body
• Inlines — Embedded images with base64-encoded content
• Attachments — File attachments with type, name, and base64 content

Delivery & Reliability

Responses with 2xx status codes indicate successful delivery. The system attempts two additional retries for 4xx or 5xx responses before stopping attempts.

Security

ImprovMX recommends IP whitelisting for webhook verification. All webhooks originate from the static IP: 15.237.103.194