How Mailhuset works

A short tour of the pieces.

Projects

A project is an isolated sending environment (its own domains, API keys, webhooks, and activity). Use separate projects for production and staging, or per app. Switch projects from the selector in the dashboard.

Verified domains

You send from addresses on a domain you've verified. Verification means publishing DNS records (SPF, DKIM, and a return-path) so mailbox providers can confirm the mail is really from you. Unauthenticated mail lands in spam. This is the single most important setup step. See Verify a sending domain.

Sending

Send over the REST API (POST /v1/email) or SMTP. A send is accepted, queued, and handed to the upstream mail infrastructure; you then track its state through delivery. Two streams exist: transactional (default) for one-to-one mail like receipts and resets, and broadcast for bulk.

Message lifecycle

Every message moves through states you can see in Activity and receive as webhooks: accepted → sent → delivered, plus opened / clicked (with tracking on), and the failure states bounced, complained (spam report), and suppressed.

Suppressions

To protect your reputation, Mailhuset keeps a suppression list: addresses that hard-bounced, complained, or unsubscribed are automatically skipped on future sends. See Suppressions.

Keys, webhooks, SDKs

Automate everything with an API key, react to events with webhooks, and integrate fast with the Node & Python SDKs.

What you're billed on

Your plan sets a monthly email allowance; usage and invoices (including mobile-money options) live on the Billing page.

Need help? Email support@mailhuset.com.