Throwaway mailboxes over curl.
Spin up mailboxes programmatically, pull inboxes via REST, or get messages pushed via webhook. Made for CI, QA suites and anti-bot workflows.
01$ curl -X POST https://api.mailiy.com/v1/mailbox \02 -H 'Authorization: Bearer mly_***********' \03 -d '{ "ttl": 1800 }'0405→ 201 Created06{ "address": "f4r1y2@mailiy.com",07 "expires_at": "2026-05-13T18:42:00Z" }
The Mailiy REST API creates and manages disposable mailboxes programmatically — built for Playwright and Cypress tests, CI pipelines, anti-bot workflows, and anything that needs mailboxes at runtime. Authentication is a bearer token in the Authorization header. You generate API keys from your account settings; they are prefixed with ml_pk_ and can be rotated at any time.
The typical flow is three calls: POST /v1/mailbox creates a fresh address (optionally with ttlMinutes), GET /v1/mailbox/:id/messages polls incoming mail, DELETE /v1/mailbox/:id cleans up at the end. If you prefer to work synchronously, register a push via POST /v1/webhooks against your own URL and receive incoming mail as a JSON event. Rate limits are predictable per tier — the Free plan ships 500 calls per month at 10 req/min, enough for a small CI suite.
Free
Lite
Pro
Business
Enterprise
REST endpoints
v1 · stableWe do not ship an official SDK because the API is small enough that curl, fetch or any HTTP client is sufficient. TypeScript examples for Playwright and Cypress live in the blog posts; PHP, Python and Go clients are community contributions. All endpoints are v1 stable — breaking changes are announced at least 90 days in advance by email to all active API key holders.
If your use case needs more than the Pro plan covers (more than 100,000 calls/month, more than 300 req/min, guaranteed SLA, dedicated Slack support channel), email sales@mailiy.com. We have Business and Enterprise tiers with a dedicated TAM and custom-domain pools, but they only make sense at meaningful volume — at smaller volume Pro is almost always the right tool.