Pricing

Rating

Developer

Actor stats

Categories

Share

📧 Temp Email — Disposable Inbox, OTP & Verification Catcher

👁 Temp Email — disposable inbox, OTP & verification-code 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.

🤖 For AI agents — MCP & Standby (on-demand inbox)

Run this Actor in Standby mode and it exposes a warm HTTP + MCP endpoint, so an AI agent can grab a throwaway inbox and catch the sign-up OTP within a single session — no cold start per call.

• MCP tools: create_inbox (→ address + key) and read_inbox (→ messages + extracted firstCode / OTP, with optional waitTimeout).
• Plain REST (same endpoint):
  • GET /?action=create&domain=auto → { address, key }
  • GET /?action=read&address=<addr>&key=<key>&waitTimeout=30&matchSubject=code → messages + firstCode

Typical agent flow: create_inbox → sign up with the address → read_inbox(waitTimeout=30) → read firstCode. Turn on Standby in the Actor's settings to get your endpoint URL.

📮 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:

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

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.

💡 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 instant check (waitTimeout 0) that finds nothing is free. If you ask the Actor to wait for mail (waitTimeout > 0) and it actually has to poll, a single small watch charge applies for that run — so a fast lookup stays cheap while waiting is priced separately.
• 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.