Developer automation

Disposable email API for verification workflows.

mailfab gives product engineers and QA teams a practical temporary inbox layer: API key authentication, mailbox creation, message reads, optional sending, webhooks, and a CLI built for repeatable automation.

Sign in for API keys Try guest inbox Testing workflow

API key authentication

Authenticated API requests use an API key header and map back to the same user mailbox ownership model as the web console.

Mailbox and message lifecycle

Create temporary addresses, list mailboxes, list messages, read message content, send from enabled addresses, and delete mailboxes or messages.

Webhook delivery

Signed-in users can configure webhook notifications for new inbound mail, including standard endpoints and supported Feishu bot URLs.

API surface for temporary inbox automation

MethodRoutePurpose

POST/api/emails/generateCreate a temporary mailbox

GET/api/emailsList active mailboxes

GET/api/emails/{id}List messages for one mailbox

GET/api/emails/{id}/{messageId}Read one message

DELETE/api/emails/{id}Delete a mailbox

What this API is not

Semrush data showed demand for disposable email checker APIs. Mailfab should not imply it provides a domain checker until that product actually exists.

Mailfab is not a disposable domain checker or blocklist lookup API.

Mailfab does not ship an official Playwright, Cypress, or Selenium SDK.

Your test runner remains responsible for extracting product-specific OTP codes, magic links, or assertions from message content.

Reliable test shape

Keep email assertions outside fragile shared inboxes.

A temporary address per scenario keeps verification mail isolated. The guest inbox is useful for quick manual checks, while signed-in workflows unlock API keys, CLI automation, webhooks, sharing, and sending where your account is allowed to send.

Playwright email testing Send from temporary email Browser-scoped guest inbox

Automation flow

1Create a mailbox for a signup, invite, password reset, or QA flow.
2Trigger the product action that sends the verification email.
3Read the inbound message through the API or CLI, then extract the needed link or code in your own test runner.
4Delete the mailbox or message when the scenario is complete.

Built for real developer surfaces.

mailfab intentionally separates quick browser use from authenticated automation. Guest inboxes are scoped to the current browser session; API and CLI workflows belong to signed-in accounts.

API keys

CLI JSON

Webhooks