Pricing

Context: emails are received at {namespace}.{tag}@inbox.testmail.app

All emails within a namespace can be accessed by any API keys authorized for the namespace. Multiple namespaces allow better access controls since you can enforce requiring different API keys to access different sets of mailboxes.

Your namespace is randomly generated by default (example: xd8a0); custom namespaces allow you to use memorable phrases like the name of your organization or team (example: acmeinc). This is more convenient since you won't have to remember or lookup the random namespace.

Context: emails are received at {namespace}.{tag}@inbox.testmail.app

The tag can be any valid string (you make it up!) allowable in an email address. By using tags, you get an unlimited number of email addresses and inboxes within each namespace. Tags are also the best (most performant) way to filter emails when retrieving them.

Example: when you send emails to acmeinc.john.smith@inbox.testmail.app, the emails are received in the john.smith inbox inside the acmeinc namespace.

You can control which namespaces each API key has access to and monitor API usage separately for each API key. This is most useful when you have multiple projects, teams, or test stages/environments.

Yes, you can send attachments. We recommend keeping the total email message size below 5 MB for best performance. Emails above 10 MB will take longer to process, and emails above 20 MB are automatically rejected.

If you are concerned about breaching any other limits, please reach out - we'd love to understand your use case.

We are happy to support open source projects, non-profits, and students/teachers (for educational use) - please contact us.