Documentation
InboxRhino is a receive-only test-email API. These pages are the public contract: how to create an inbox, wait for real mail, and clean up so quota is released. There is no send endpoint. Use the REST API directly; official SDK packaging is planned only after the API surface is stable.
Guides
- API quickstart
Create a key, provision a real inbox, wait for the message, delete the inbox. About five minutes.
- API reference
Authentication, quotas, wait-for-message, errors, OpenAPI, and the Postman collection.
- Playwright email testing
Assert signup, OTP and password-reset mail from Playwright without a plugin.
How an InboxRhino email test works
1. Create an inbox
POST /v1/inboxes returns a fresh address on test.inboxrhino.in. Each test gets its own inbox, so parallel runs never read each other's mail.
2. Trigger the email
Sign up, request a password reset, or ask for an OTP in your app using that address. Your real mailer delivers it; there is nothing to rewire.
3. Wait for the message
GET /v1/inboxes/{id}/messages with wait_seconds holds the request open for up to 180 seconds and can filter by subject or sender. No sleep loops.
4. Assert, then delete
Read the parsed text or HTML, extract the code or link, and assert on it. Delete the inbox afterwards to release the active-inbox quota.
Developer resources
Import the downloadable Postman collection or generate a client from the OpenAPI specification. Quotas and GST status are on InboxRhino pricing. Choosing between tools? See the Mailosaur alternative and MailHog alternative comparisons.