Skip to main content

Wildmail documentation

Wildmail gives each customer an individual account with a hosted test address. Connect a webhook and receive a signed event before changing DNS, then verify a customer-owned domain to receive mail there. The dashboard provides message search, delivery history, raw message downloads, and replay while the account's current retention policy permits access.

SMTP acceptance confirms durable message storage. It does not mean webhook delivery succeeded. Wildmail prepares delivery from the stored message after acceptance. Retained-message deliveries can retry within their delivery window. With 0-day retention, Wildmail allows at most one webhook attempt and does not allow automatic retry or replay. See usage and retention for the current retention behavior.

Start with the quickstart, then implement signature verification. Read delivery and replay before performing business actions from events. The API reference describes the customer HTTP routes, permissions, and request examples.

For document intake, receive mail at an address such as invoices@intake.example.com, verify the signature, and store the stable event ID with your application's database change. With positive retention, fetch attachments before content expires. With 0-day retention, use the attachment bytes included in the webhook. Sender authentication results are useful signals for your application's review policy.

Standard events contain parsed message data, authentication results, attachment metadata, and the envelope addresses matched by Wildmail. Optional payload shaping can select, rename, and nest these fields for an endpoint. It does not extract new data or validate customer-defined schemas. Integrations should use the documented event format and perform any application-specific extraction or validation in their own receiver.