Temp Email | Disposable Inbox, OTP & Verification Catcher avatar

Temp Email | Disposable Inbox, OTP & Verification Catcher

Pricing

from $10.00 / 1,000 message receiveds

Go to Apify Store
Temp Email | Disposable Inbox, OTP & Verification Catcher

Temp Email | Disposable Inbox, OTP & Verification Catcher

Create a disposable email inbox and read incoming messages on demand: OTP codes, sign-up confirmations and verification links. Wait for a specific email, auto-extract codes and magic-link tokens, read attachments and headers. Keyless, no signup. For QA, automation and signup testing.

Pricing

from $10.00 / 1,000 message receiveds

Rating

0.0

(0)

Developer

Apivault Labs

Apivault Labs

Maintained by Community

Actor stats

0

Bookmarked

20

Total users

1

Monthly active users

4 days ago

Last modified

Share

๐Ÿ“ง Temp Email โ€” Disposable Inbox, OTP & Verification Catcher

Spin up a disposable email inbox in seconds and read its incoming messages โ€” one-time codes (OTP), sign-up confirmations and verification links โ€” on demand. Perfect for QA, test automation, sign-up flows, scraping pipelines and bots that need a throwaway mailbox.

No API key, no registration. Create an inbox instantly, then read it on demand with built-in OTP/verification-code extraction.


๐Ÿ“ฎ Available domains

Just pick a domain from the dropdown when you create the address:

  • Auto โ€” the fastest, most reliable random address (recommended).
  • Branded custom domains: @swagpapa.com ยท @rulersonline.com ยท @besttempmail.com ยท @deepmails.org ยท @embassybase.com ยท @justdefinition.com ยท @gongjua.com ยท @123mails.org
  • Gmail aliases: dot trick (a.b.c@gmail.com), plus trick (abc+tag@gmail.com), Googlemail (a.bc@googlemail.com).

Reading: Auto inboxes are read with their key (token). Branded and Gmail inboxes can be read with just the address โ€” leave the key empty.


โœจ Highlights

  • ๐Ÿ“จ Create a throwaway inbox instantly โ€” pick any domain, get the address + credentials in ~1 second.
  • ๐Ÿ“ฅ Read on demand โ€” when you expect a message, run read on the inbox; it polls until the mail lands (great for catching a verification email after a sign-up).
  • ๐Ÿ”‘ OTP & link extraction โ€” pulls likely one-time codes and verification/confirmation links out of the message body.
  • ๐ŸŽฏ Wait for the right email โ€” filter by sender, subject or keyword and keep polling until the email you actually want arrives (ignore inbox noise and old mail).
  • ๐Ÿ“Ž Attachments โ€” see attachment metadata (filename, type, size, download URL) on each message.
  • ๐Ÿ“ฆ Bulk create โ€” spin up many inboxes in a single run for load and parallel QA testing.
  • ๐Ÿ›ก๏ธ Reliable by default โ€” create retries automatically and falls back to the fast Auto pool if a branded inbox is unavailable.
  • ๐Ÿท๏ธ Branded domains & Gmail aliases โ€” varied addresses, or a fast random one.
  • ๐Ÿ”‘ Read by address โ€” branded/Gmail inboxes open with just the email (no key to keep).
  • ๐Ÿ” Re-readable โ€” the create result carries the inbox credentials so you can read the same inbox any time.
  • ๐Ÿ†“ Keyless โ€” no key, no signup, no proxy.

๐Ÿง  How it works

Two simple, separate steps:

ActionWhat it does
create (default)Makes a new inbox and returns its address + credentials instantly (~1s). No waiting.
readChecks an existing inbox for messages. Pass the address + credentials from a create run; it polls up to waitTimeout for new mail.

Typical automation flow:

  1. Run create โ†’ get the address (+ token/password or code).
  2. Use the address to sign up somewhere / trigger a mail.
  3. Run read with that address + credentials โ†’ get the message and the extracted firstCode.

๐Ÿ“ฅ Input

FieldTypeDefaultDescription
domainstringautoPick the address domain: auto, a branded domain, or a Gmail alias.
actionstringcreatecreate (new inbox, instant) or read (check an existing inbox).
usernamestringโ€”Local part for the Auto domain (random if empty).
countinteger1create only: number of inboxes to create in one run (1-25).
allowFallbackbooleantruecreate only: fall back to a reliable Auto inbox if a branded/Gmail inbox fails.
addressstringโ€”Inbox address (for action=read).
inboxesarrayโ€”read only: check several inboxes in one run, e.g. [{"address":"a@x.com","key":"..."}].
token / passwordstringโ€”Credentials for an Auto inbox (for read).
codestringโ€”Credential for a branded/Gmail inbox (for read).
waitTimeoutinteger0read only: 0 = check once and return instantly (fast). Set >0 to wait for mail.
pollIntervalinteger6read only: seconds between inbox checks.
matchFromstringโ€”read only: keep waiting until an email from a sender containing this text arrives.
matchSubjectstringโ€”read only: only return emails whose subject contains this text.
matchKeywordstringโ€”read only: only return emails containing this text anywhere (subject/body).
onlyUnseenbooleanfalseread only: skip messages already marked as seen.
waitForNewbooleanfalseread only: ignore mail already in the inbox when the run starts.
latestOnlybooleanfalseread only: return just the newest matching message.
maxMessagesinteger0read only: cap how many matching emails to return (0 = no limit).
extractCodesbooleantrueExtract OTP codes and verification links.
includeBodybooleantrueInclude full text/HTML body per message.
codeMinLength / codeMaxLengthinteger4 / 8Length range for OTP code detection.
codeRegexstringโ€”Advanced: custom regex to extract the code yourself.
includeRawbooleanfalseAlso return raw EML + parsed headers and SPF/DKIM/DMARC (Auto inboxes only).

Example: create an inbox (instant)

{
"action": "create",
"domain": "auto"
}

Example: create several inboxes at once

{
"action": "create",
"domain": "auto",
"count": 10
}

Example: branded address, then read it later

{ "action": "create", "domain": "swagpapa.com" }
{ "action": "read", "address": "abc@swagpapa.com" }

Add "waitTimeout": 60 to a read if you want it to keep waiting for an incoming mail instead of returning instantly.

Example: wait for the verification email from a specific sender

{
"action": "read",
"address": "abc@swagpapa.com",
"matchFrom": "no-reply@service.com",
"waitForNew": true,
"latestOnly": true,
"waitTimeout": 90
}

This keeps polling (ignoring anything already in the inbox) until a fresh email from service.com lands, then returns just that one message with its extracted firstCode.

Example: check several inboxes at once

{
"action": "read",
"inboxes": [
{ "address": "a@swagpapa.com" },
{ "address": "u4f9k2@example.net", "key": "eyJ0eXAiOiJKV1Q..." }
]
}

Takes one snapshot per inbox. Branded/Gmail addresses open with just the address; Auto addresses need their key (token).


๐Ÿ“ค Output

create โ†’ one item with the new inbox address and its credentials:

{
"success": true,
"address": "u4f9k2@example-domain.com",
"token": "eyJ0eXAiOiJKV1Q...",
"password": "โ€ฆ",
"messageCount": 0
}

read โ†’ one dataset item per email (so a 3-message inbox = 3 results). Each item is a full message:

{
"success": true,
"address": "u4f9k2@example-domain.com",
"messageIndex": 1,
"messageCount": 2,
"id": "โ€ฆ",
"from": "no-reply@service.com",
"fromName": "Service",
"subject": "Your verification code",
"text": "โ€ฆ",
"html": "โ€ฆ",
"otpCodes": ["424864"],
"verificationLinks": ["https://service.com/verify?token=โ€ฆ"],
"firstCode": "424864",
"token": "eyJ0eXAiOiJKV1Q..."
}

If the inbox is empty, read returns a single summary item with messageCount: 0 and the inbox credentials so you can read again later.

FieldDescription
addressThe disposable inbox address.
token / password or codeCredentials to re-read this inbox later.
messageIndex / messageCountPosition of this email and the total found this read.
from / fromName / subjectSender and subject of the email.
text / htmlFull message body.
otpCodes[] / verificationLinks[]Extracted one-time codes and verification links.
verificationTokens[]Token-like values pulled from verification link query params (e.g. magic-link / passwordless tokens).
firstCodeThe first extracted OTP code of this message (handy shortcut).
hasAttachments / attachments[]Whether the email has attachments, and their metadata (filename, contentType, size, downloadUrl).
raw / headers / authResultsRaw EML source, parsed headers and the Authentication-Results line (when includeRaw is on, Auto inboxes).
spf / dkim / dmarcAuthentication verdicts parsed from the headers (pass / fail), when available.

๐Ÿ’ก Use cases

  • Automated sign-up / account testing โ€” catch the confirmation email and code.
  • QA & end-to-end tests โ€” verify your product's transactional emails.
  • Scraping & bots โ€” register throwaway accounts that need email verification.
  • OTP capture โ€” pull the one-time code straight into your workflow.

โš™๏ธ Notes & limits

  • Billed per inbox created and per message retrieved โ€” create = one charge for the new inbox; read = one charge per email delivered. An empty read (no mail yet) is free, so you can poll an inbox while waiting without paying for nothing.
  • create is instant; read checks once by default (waitTimeout 0) โ€” set waitTimeout to keep waiting for mail to arrive.
  • Disposable inboxes are short-lived by nature; read them promptly.
  • Branded inboxes are rate-limited, so read uses a safe minimum poll interval automatically.

Built and maintained by Apivault โ€” reliable data Actors, fair pricing.


Please read this section carefully. By running this Actor you accept these terms.

Bottom line: this is a neutral, general-purpose software tool. It only retrieves information that is already publicly available. You โ€” the user โ€” decide what to search for and how to use the results, so you alone are responsible and liable for that use. The developer/operator of this Actor merely provides the tool and does not control, endorse, or take responsibility for what you do with it.

1. Public data only. The Actor accesses only publicly available information. It does not log in on your behalf, bypass access controls, or retrieve private, paywalled, or password-protected data.

2. You are the responsible party (data controller). For every run you start, you act as the data controller and are solely responsible for using the output lawfully. This includes having a valid lawful basis (for business/B2B use this is typically legitimate interest), honoring data-subject rights (access, correction, deletion, opt-out), and complying with all applicable laws and regulations โ€” including, where relevant, the GDPR, UK GDPR, CCPA/CPRA, and similar privacy, marketing, and anti-spam laws (e.g. ePrivacy, CAN-SPAM, CASL, TCPA).

3. Not a Consumer Reporting Agency. This Actor and its operator are not a consumer reporting agency (CRA), and the output is not a "consumer report" under the U.S. Fair Credit Reporting Act (FCRA) or similar laws. You must NOT use it, in whole or in part, to decide a person's eligibility for credit, employment, housing/tenancy, insurance, or any other FCRA-regulated purpose.

4. Respect third-party terms. You are responsible for complying with the terms of service of any website or platform whose public data you choose to process, and with any applicable intellectual-property rights.

5. No warranty. The Actor is provided "as is", without warranty of any kind. Public data may be incomplete, outdated, or inaccurate โ€” verify independently before relying on it. Availability of sources and fields can change at any time.

6. Prohibited use. Do not use this Actor or its output for stalking, harassment, discrimination, fraud, spam, or any unlawful or harmful purpose.

7. Indemnification. You assume all risk and liability arising from your use of this Actor, and you agree to defend, indemnify and hold the operator harmless from any and all claims, losses, fines, or liabilities โ€” including reasonable legal fees โ€” resulting from your use or misuse of the Actor or its output, or from your breach of these terms or of any law.

This section is general information, not legal advice. If you are unsure whether your intended use is permitted, consult your own legal counsel before running this Actor.