Last updated:
The eTempMail API lets developers create disposable inboxes and poll for messages during QA, signup-flow tests, and continuous integration — for positive, lawful use only. Production credentials and interactive docs live on RapidAPI.
Open Temp Mail API on RapidAPI
Who this API is for
- QA engineers verifying email confirmation and password-reset flows
- Developers writing Playwright, Cypress, or PHPUnit tests that need a throwaway inbox
- Teams that need programmatic access within RapidAPI plan limits
Not for: spam sending, bulk abusive signups, ban evasion, or any use that breaks third-party terms.
Quick start on RapidAPI
- Open the Temp Mail API listing and subscribe to a plan.
- Copy your RapidAPI key from the developer dashboard.
- Call the documented endpoints to create an inbox, then poll for messages until the confirmation arrives or your test times out.
Create an inbox (curl example)
Exact paths and parameter names follow the live RapidAPI docs. Pattern:
curl -X GET "https://temp-mail-api3.p.rapidapi.com/..." \
-H "x-rapidapi-host: temp-mail-api3.p.rapidapi.com" \
-H "x-rapidapi-key: YOUR_RAPIDAPI_KEY"
Replace the path with the create-inbox (or equivalent) operation shown on RapidAPI. Store the returned address for the next step.
Poll for messages (curl example)
curl -X GET "https://temp-mail-api3.p.rapidapi.com/..." \
-H "x-rapidapi-host: temp-mail-api3.p.rapidapi.com" \
-H "x-rapidapi-key: YOUR_RAPIDAPI_KEY"
Poll with a short backoff (for example every 2–5 seconds) until the expected subject arrives or your test deadline is reached. Do not hammer the API beyond your plan’s rate limits.
Rate limits and free / paid tiers
- Limits are enforced by your RapidAPI subscription for the public API listing.
- Temp Mail Pro dashboard plans separately include monthly API call quotas (Starter about 3k/month; Pro about 10k/month) for Pro product features — see Pricing.
- If you receive HTTP 429 responses, slow down and check your remaining quota.
Use in Playwright
// Pseudocode — wire to the RapidAPI operations you subscribe to
const inbox = await createTempInbox(apiKey);
await page.fill('input[type=email]', inbox.address);
await page.click('button[type=submit]');
const message = await waitForMessage(apiKey, inbox.id, /verify|confirm/i, 60_000);
const link = extractFirstHttpUrl(message.body);
await page.goto(link);
Use in Cypress
cy.task('createTempInbox').then((inbox) => {
cy.get('input[type=email]').type(inbox.address);
cy.contains('button', /sign up|continue/i).click();
cy.task('waitForMessage', { inboxId: inbox.id, timeout: 60000 })
.then((message) => {
const link = extractFirstHttpUrl(message.body);
cy.visit(link);
});
});
Implement createTempInbox / waitForMessage in Cypress tasks using the same RapidAPI HTTP calls as curl.
CI tips
- Keep RapidAPI keys in CI secrets — never commit them.
- Fail tests cleanly on timeout rather than looping forever.
- Use disposable domains only on staging systems that allow them.
Related tools on eTempMail
- Free temp mail inbox (browser UI)
- 10 Minute Mail and other timed modes
- Temp mail for software testing (guide)
- FAQs on retention and pricing
Questions: [email protected]