Receive verification codes and test sign-up emails

To receive verification codes for a sign-up or a test, create a nicemails mailbox and enter its address in the form. The code arrives like any other email. Read it in the web app, fetch it with the REST API, or ask an AI agent to find it over MCP. Plus addressing lets one mailbox take many sign-ups.

Why use a real mailbox instead of a temporary email site?

A nicemails mailbox belongs to your account. Its mail is available to you and to the apps and keys you connect, not to anyone who happens to know or guess the address.

Mail stays until you delete it, so a code or a confirmation link is still there when you come back to it. When you delete a mailbox, its address is retired and never issued again, so nobody can later receive a password reset for an account you registered with it.

nicemails is not an anonymous throwaway service. You need an account, mailbox creation is limited, and the Acceptable Use Policy does not allow creating accounts or mailboxes in bulk. It is made for legitimate sign-ups and for testing your own sign-up flows.

How do I receive a verification code?

Create a mailbox, for example signup-tests.
Enter its address in the sign-up form. To keep test runs apart, add a tag after a plus sign: mail to signup-tests+run1@… arrives in the signup-tests mailbox.
Open the mailbox in the web app. New mail appears without reloading the page.
Copy the code from the message. If it is not in the Inbox, look in Spam.
When you are done, keep the mailbox for the next run, disable it to reject new mail, or delete it.

How do I read codes automatically in tests?

Create an API key with the Read permission in Settings → API keys and limit it to the test mailbox. Send it as Authorization: Bearer <key> and call the REST API:

GET /v1/mailboxes/{id}/messages lists the Inbox, newest first.
GET /v1/mailboxes/{id}/messages/{mid} returns one message with its body.
GET /v1/mailboxes/{id}/search?q= searches the mailbox.

Reading and managing mail through the API is included on Free; sending through the REST API requires Pro. The REST API reference lists every endpoint.

With an AI agent, connect over MCP and ask it to find the latest code in the test mailbox. Its search tool covers every folder, including Spam, and get_message reads a message without marking it as read. See the setup guide.

What limits apply to test mailboxes?

Free: 3 mailboxes and 3 GB of storage, with at most 3 new mailboxes per UTC month.
Pro, $10 a month: 100 mailboxes and 10 GB of storage.
Any account can create up to 20 mailboxes per UTC day.
Receiving is unlimited within your storage, and tags after a plus sign never use up a mailbox.
Mail in Spam is deleted after 30 days.

Because a deleted address can never be created again, give a mailbox you reuse for tests a stable name and tell runs apart with tags. See Pricing for every limit.

Common questions

Can I use one mailbox for many test sign-ups?

Yes. Mail sent to name+anything@ is delivered to the name@ mailbox, so each run can use its own tag without creating another mailbox.

Can I read codes with the API on the Free plan?

Yes. An API key with the Read permission can list, search and read mail on Free. Sending through the REST API requires Pro.

Is nicemails a disposable email service?

No. Mailboxes belong to your account and keep mail until you delete it. You need an account, mailbox creation is limited, and creating accounts or mailboxes in bulk is not allowed.

What happens when I delete a test mailbox?

Its address is retired permanently, and the mailbox and its messages are scheduled for deletion. Nobody, including you, can create that address again.

Related guides

Start for free