emailnator.com APIwww.emailnator.com ↗
Generate disposable Gmail and custom-domain email addresses and read incoming messages via the Emailnator API. Supports dot-trick, plus-addressing, and more.
curl -X GET 'https://api.parse.bot/scraper/17c1b5ae-23d5-41ca-94da-5245ffef3f58/generate_email?email_types=dotGmail%2CplusGmail%2CgoogleMail' \ -H 'X-API-Key: $PARSE_API_KEY'
Generate a new temporary/disposable email address. Supports different email types: dotGmail (Gmail dot trick), plusGmail (Gmail plus addressing), googleMail (@googlemail.com), and domain (custom @femailtor.com domain).
| Param | Type | Description |
|---|---|---|
| email_types | string | Comma-separated list of email generation types. Accepted values: dotGmail, plusGmail, googleMail, domain |
{
"type": "object",
"fields": {
"email": "string - the generated email address",
"email_types_used": "array of strings - the email types used for generation"
},
"sample": {
"data": {
"email": "[email protected]",
"email_types_used": [
"dotGmail",
"plusGmail",
"googleMail"
]
},
"status": "success"
}
}About the emailnator.com API
The Emailnator API exposes 3 endpoints for creating temporary email addresses and reading their inboxes without a permanent account. The generate_email endpoint produces addresses across four generation strategies — dotGmail, plusGmail, googleMail, and a custom femailtor.com domain — while get_messages and get_message let you list and read incoming mail by message ID.
Generating Temporary Email Addresses
The generate_email endpoint accepts an optional email_types parameter as a comma-separated string of one or more strategies: dotGmail (Gmail dot-trick variations), plusGmail (Gmail plus-addressing), googleMail (@googlemail.com alias), or domain (@femailtor.com). The response returns the generated email address as a string and an email_types_used array confirming which strategies were applied. If email_types is omitted, the API selects a default strategy.
Reading the Inbox
Once you have an address, pass it to get_messages to retrieve the inbox list for that address. The response includes the email string, a total integer count of messages, and a messages array. Each item in that array carries a messageID, from, subject, and time field — enough to identify a specific message without fetching its full body. Advertising and promotional placeholder messages are filtered out automatically before the response is returned.
Fetching Full Message Content
To retrieve the body of a specific email, call get_message with both the email and message_id (taken from the messageID field in get_messages). The response includes a content_html field containing the raw HTML body when the message is HTML-formatted, or a content object when the message is JSON-formatted. Both the email and message_id are echoed back in the response for reference.
Coverage Notes
All generated addresses are ephemeral — there is no persistent account. Inboxes are only accessible while the generated address remains valid. The API does not expose controls for setting inbox expiry, deleting messages, or sending outbound email.
- Automate account sign-up flows in CI pipelines using freshly generated dotGmail addresses from
generate_email - Poll
get_messagesto detect when a verification email arrives, then parse the subject or body fromget_message - Use plusGmail addresses to test how a service handles plus-addressed emails during QA
- Generate @googlemail.com aliases to verify inbox delivery for region-specific email configurations
- Extract OTP codes or confirmation links from
content_htmlreturned byget_messagein end-to-end test suites - Spin up isolated inboxes per test case using the
domaintype to avoid cross-test message contamination
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Emailnator have an official developer API?+
What does `get_messages` return, and how are messages filtered?+
get_messages returns a messages array where each object contains a messageID, from, subject, and time. It does not return full email bodies — those require a separate get_message call using the messageID. Advertising and promotional placeholder entries are filtered out before the response is delivered, so only real incoming messages appear.Can I retrieve attachments or raw MIME content from emails?+
get_message returns either a content_html string (HTML body) or a content object (JSON-formatted responses). Attachment data and raw MIME parts are not exposed. You can fork this API on Parse and revise it to add an endpoint that surfaces attachment metadata or raw message content.Is there a way to list or reuse previously generated email addresses?+
generate_email call and does not maintain a session or history of previously created addresses. You can fork this API on Parse and revise it to add persistence logic or a listing endpoint backed by your own storage layer.What happens if I call `get_messages` before any mail has arrived?+
messages array that is empty and a total of 0. The email field will still reflect the address you passed in, so you can poll the endpoint and compare total to detect when new mail arrives.