Rabbinatix
Sign inGet started
Store

Verify an email address

FreeFlow
@rabbinatix/verify-an-email-address by Rabbinatixupdated Oct 13, 2026

A new user opens the link from the welcome email; the auth service checks it once, and an expired link offers a new one.

Sign up to use it

The "confirm your email" step after sign-up:

  • Client app opens the link, sends its token and shows the answer, with a "Send a new link" offer when it makes sense.
  • Auth service finds the link, refuses an unknown (404) or expired (410) one, marks the email verified and uses the link up.
  • User store keeps the links and the users. Event bus (optional) receives user.email_verified.

Opening the same link twice is fine: the second time says it was already verified, instead of an error.

Tricky step: the user store answers whether the link has expired (expires_at < now()), so the clock that decides is the database’s, not each server’s.

Previewlanes are roles; you pick your systems when importing
Not found400404410Other
Start in Client app. step 1 of 19. key stepOn Open verification link
Call to another system in Client app. step 2 of 19. key stepCall verify email
Start in Auth service. step 3 of 19. key stepOn POST /api/v1/email-verification
Resource in Auth service. step 4 of 19. key stepFind the link
Answer in User store. step 5 of 19. key stepemail_verifications.findByToken
Return in Auth service. step 6 of 19. key stepOpened twice → same 200
Return in Auth service. step 7 of 19. key stepExpired link → 410
Resource in Auth service. step 8 of 19. key stepMark the email verified
Answer in User store. step 9 of 19. key stepusers.markEmailVerified
Resource in Auth service. step 10 of 19Use up the link
Answer in User store. step 11 of 19. key stepemail_verifications.use
Return in Auth service. step 12 of 19. key stepVerified → 200
Return in Auth service. step 13 of 19. key stepUnknown link → 404
Return in Auth service. step 14 of 19. key stepNo token → 400
Return in Client app. step 15 of 19. key stepReturn
Return in Client app. step 16 of 19. key stepReturn
Return in Client app. step 17 of 19. key stepReturn
Return in Client app. step 18 of 19. key stepReturn
Return in Client app. step 19 of 19. key stepReturn
Client app
Web frontend
Auth service
Backend service
User store
Database

Up and down arrows: previous or next step. Home, End: first or last. Enter: select. Shift F10: more actions.

APIs
POST{base}/email-verification· Verify an email address with the emailed link
Auth service provides it · Client app calls it
Request body
token: string
200
message: string
400
error: string
404
error: string
410
error: string
Data operations
email_verifications.findByTokenqueryon User store(token: string)
users.markEmailVerifiedupdateon User store(userId: string)
email_verifications.useupdateon User store(token: string)
Test cases
Fresh link verifies the email→ Verified
Expired link→ Expired, a new link can be sent
Link opened twice→ Verified already
Unknown link→ Not a valid link
Link without a token→ No token in the link
Verifying publishes user.email_verified→ Verifiedwith “Publish user.email_verified”
Requirements
A link verifies the email once; opening it again says it is verified already.
An expired or unknown link verifies nothing and offers a new link.
Roles (4)
Client app
Where the verification link opens · Web frontend or mobile app
Auth service
Checks the link and marks the email verified · Backend service
User store
Database with the users and verification links · Database
Event bus (optional)
Receives user.email_verified (optional) · Queue / event bus
Settings
Publish user.email_verifiedoff
Link token fieldtoken (renamable)
Versions