Tempboxy
Tempmail API Free · Public JSON REST v1

Tempmail API free.

Free tempmail REST API with zero signup walls. Provision .com or .edu.pl disposable mailboxes and fetch normalized messages, attachments, and OTP codes in JSON.

Zero-friction free tempmail API for developers & QA

The Tempboxy tempmail API free endpoint (/api/v1) gives developers programmatic access to standard (.com) and academic (.edu.pl) inboxes without signup walls or credit cards. Create an inbox with POST /api/v1/inboxes (10m–7d or never TTL), read enriched messages at /messages, or pull the latest OTP code directly at /code.

Reference

REST v1 endpoints

EndpointPayload / QueryDescription
GET/api/v1/domains?provider=tempmail|edumailList live active .com and .edu.pl domains.
POST/api/v1/inboxes{ provider, alias, domain_id, ttl }Create inbox & receive signed recovery_token.
POST/api/v1/inboxes/restore{ recovery_token }Validate expiration & restore inbox messages.
PATCH/api/v1/inboxes/:id/ttl{ ttl: "10m"|"1h"|"24h"|"7d"|"never" }Extend, shorten, or set no-expiry inbox lifetime.
GET/api/v1/inboxes/:id/messages—Fetch messages with OTPs, attachments & security audit.
GET/api/v1/inboxes/:id/code—Pull the newest verification code & magic link.
DEL/api/v1/inboxes/:id—Burn the temporary address upstream.

Step-by-step tutorial: Automating Signup & OTP Tests in Playwright & Python →

Questions

Frequently asked

Is the Tempboxy disposable email API really free without an API key?

Yes. All /api/v1 endpoints work directly out of the box with polite IP fair-use rate limiting and zero registration.

Does the API support both .com and .edu.pl domains?

Yes — send {"provider": "tempmail"} for standard .com domains or {"provider": "edumail"} for .edu.pl domains to POST /api/v1/inboxes and use identical /messages and /code endpoints.

What fields does GET /api/v1/inboxes/:id/messages return?

Each message includes id, from, from_name, subject, date, text_body, html_body, verification_code, verification_links, attachments, and security (pixels, UTM count, spamScore, riskLevel).

Can I pick a custom alias and specific domain via the API?

Yes. Fetch active domain IDs from GET /api/v1/domains and pass alias and domain_id in your POST /api/v1/inboxes JSON body.

Does the API allow browser CORS requests?

Yes. All /api/v1 endpoints return Access-Control-Allow-Origin: * headers for GET, POST, PATCH, and DELETE.

How should I poll for OTP emails in automated CI tests?

Poll GET /api/v1/inboxes/:id/code every 2–4 seconds with a 30-second timeout, then call DELETE /api/v1/inboxes/:id in your teardown block.

Need more answers? Browse all 29 topics in the Complete Tempboxy FAQ.