QA guide · OTP and magic links
Test email OTP and magic-link delivery
Create a fresh inbox for each test, trigger the email flow, then read the delivered message or query the latest-code endpoint from your test runner.
Typical verification test
- Create a temporary mailbox.
- Use its address in the signup or login flow.
- Trigger the verification email.
- Poll messages or
/mailboxes/{id}/latest-code. - Submit the returned code, or extract the expected link from the message data in your test harness.
API primitives
curl -X POST https://inboxes.run/api/v1/mailboxes -H "Authorization: Bearer $INBOXESRUN_API_KEY" -H "Content-Type: application/json" -d '{}'
curl https://inboxes.run/api/v1/mailboxes/{mailbox_id}/messages -H "Authorization: Bearer $INBOXESRUN_API_KEY"
curl https://inboxes.run/api/v1/mailboxes/{mailbox_id}/latest-code -H "Authorization: Bearer $INBOXESRUN_API_KEY"Use message polling when the workflow is more complex
The latest-code endpoint is convenient for code-driven verification flows. For a magic link, custom confirmation URL or provider-specific body, read the mailbox messages and let your test code extract the value it expects.
Security boundary
Use temporary inboxes only for accounts and systems you are authorized to test. Inboxes.Run prohibits phishing, credential harvesting, account takeover and attempts to bypass third-party access controls.
Try it
Open a temporary inbox in the browser for free. For programmatic use, sign in and open API / IMAP to generate an API key and see the current limits.