Skip to content

Introducing Waridex

Most applications send email at the moments that matter most: sign-up, sign-in with a one-time code, password reset, invitations. Those are also the flows an end-to-end test suite has the hardest time covering. The test needs an address it controls, has to find the message when it arrives, and then has to dig a six-digit code or a link out of HTML that was designed for people, not parsers. Waridex is built to make that part of a test short and dependable.

A test creates an inbox, makes the app under test send its email there, and calls wait. The call holds until a matching message arrives, or returns at once if it already has, and answers with the message and, with extract=otp, the code already extracted:

Terminal window
curl -sS -G "https://api.waridex.com/v1/inboxes/$INBOX_ID/wait" \
-H "Authorization: Bearer $WARIDEX_API_KEY" \
--data-urlencode "to=user1@signup-k3f9x2.waridex.email" \
-d extract=otp

There is no polling loop in the test and no HTML parsing. Codes are found when the message arrives, by patterns you pin per sender and by deterministic scoring, never by guessing. When nothing fits, the error lists every candidate and why it lost, so a failed test tells you what the email actually said.

Every inbox has a domain of its own, such as signup-k3f9x2.waridex.email, and any address under that domain reaches it. A CI run creates one inbox, and each test invents its own recipient: user1@…, reset+42@…, or one derived from the test’s name. wait takes the exact recipient, so parallel tests sharing the inbox never take each other’s mail.

Inboxes carry tags, usually the run that created them, and one call at the end of the run deletes every inbox of the tag with its mail.

Waridex is priced per workspace, not per seat and not per inbox. A workspace groups the inboxes, API keys and patterns of one project; everyone in your organisation can use it, and your tests can create as many inboxes as they need. The plans differ only in how much mail a workspace receives each month, how long it is kept and how many patterns it pins. There is a Free plan to start with.

The curl quickstart runs a whole test in four calls, and the concepts explain inboxes, wait, extraction and keys in more detail. Every error the API returns links to a page that says what it means and what to do.

Questions and feedback are welcome at support@waridex.com.