Programmable inboxes
Use the CLI or REST API to create inboxes, read messages, and wire temporary email into tests or agent workflows.
How It Works
mailfab SEO
mailfab is built for quick verification flows, QA runs, and agent-friendly inbox automation without turning the product into a public mailbox directory.
Use the CLI or REST API to create inboxes, read messages, and wire temporary email into tests or agent workflows.
API keys are stored as SHA-256 hashes with a mailfab-specific prefix, and keys can be rotated from the console.
When a mailbox expires or is deleted, mailfab removes the mailbox and its messages from the active product data.
When an inbox expires, mailfab removes the mailbox and its messages from active product data. Create a new inbox when you need to receive more mail.
Deleting an inbox removes the mailbox and its stored messages, so they are no longer available through mailfab views, shares, or API responses.
Senders see the mailfab address you give them. Guest inboxes do not require a personal email address, while signed-in accounts use your account identity for console access.
Guest inboxes support short windows such as 10 minutes, 1 hour, or 24 hours. Registered users can choose supported mailbox lifetimes, including a no-expiry option for member inboxes.
All shares become immediately inaccessible. Anyone with a share link will see an error. Shares are tied to the inbox — when the inbox is gone, every share is revoked.
Yes. All API traffic requires HTTPS. API keys are stored as salted SHA-256 hashes — we never store plaintext keys. Keys can be revoked and rotated at any time from the developer console.
mailfab stores received messages so the inbox can display them while the mailbox is available. Expiry or deletion removes the mailbox and its messages from the product.
We recommend using mailfab for verification codes, trial signups, and testing. For long-term accounts, use a permanent email provider. Once an inbox expires, you lose access to password resets sent to that address.