☰ Docs menu · Hosted e-mail pages
Hosted e-mail pages
Abrova Auth's own pages for the confirm e-mail and password reset links, like Firebase's e-mail action handler: no page or code in your app, a Continue button back to it, one-time links that a mail scanner can't use up.
The confirm e-mail and password reset e-mails link to Abrova Auth's own pages, unless your app passes a redirectUrl. The user confirms the e-mail or chooses a new password there, and a Continue button can take them back to your app. Firebase calls this the e-mail action handler.
The two pages#
| Page | Address | What it does |
|---|---|---|
| Confirm e-mail | https://auth-users.abrova.ir/pages/verify | Shows a "Confirm e-mail" button; pressing it marks the e-mail as confirmed. |
| Password reset | https://auth-users.abrova.ir/pages/reset | Asks for the new password twice and saves it. Every session of the user ends and the e-mail counts as confirmed. |
You never build these addresses yourself: Abrova Auth puts them in the e-mail, followed by ?token=… (one use) and &lang=… (the e-mail's language, so the page speaks it too). They name no app and need no key: the token tells Abrova Auth which project it belongs to.
Step 1: When the links open them#
| Opens the hosted page when | |
|---|---|
| Confirm e-mail at sign-up | Your project requires a confirmed e-mail and you pass no redirectUrl. Without that requirement, a sign-up sends no e-mail unless you pass a redirectUrl. |
| Confirm e-mail again | You call sendEmailVerification (signed-in user) or resendVerification (not yet confirmed) without a redirectUrl. |
| Password reset | You call sendPasswordReset without a redirectUrl. |
| Magic link | Never: a magic link signs the user in to your app, so it always needs your own redirectUrl. |
The ready-made sign-in screen uses the hosted pages unless you give it verifyRedirectUrl or resetRedirectUrl.
Step 2: Back to your app with Continue#
Pass continueUrl with the call that sends the e-mail. When the page is done, it shows a Continue button to that address: a page of your site, or a link that opens your app (myapp://signed-up).
- Add the address to Abrova Auth › Settings › Link addresses, for example
https://example.com/ormyapp://. While developing you can addhttp://localhost:<port>as well. - Pass it as
continueUrl:
// Web and React Native
await auth.signUpWithEmail({ email, password, continueUrl: 'https://example.com/welcome' });
await auth.sendPasswordReset({ email, continueUrl: 'https://example.com/sign-in' });
await auth.resendVerification({ email, password, continueUrl: 'https://example.com/sign-in' });// Flutter await AbrovaAuth.instance.signUpWithEmail(email: email, password: password, continueUrl: 'myapp://welcome'); await AbrovaAuth.instance.sendPasswordReset(email, continueUrl: 'myapp://sign-in');
// iOS try await AbrovaAuth.shared.signUp(email: email, password: password, continueURL: "myapp://welcome") try await AbrovaAuth.shared.sendPasswordReset(email: email, continueURL: "myapp://sign-in")
// Android AbrovaAuth.shared.signUp(email, password, continueUrl = "myapp://welcome") AbrovaAuth.shared.sendPasswordReset(email, continueUrl = "myapp://sign-in")
On the ready-made sign-in screen, set the continueUrl option (continueURL on iOS) and every e-mail it sends uses it.
A continueUrl that is not under one of your link addresses is refused with INVALID_INPUT before any e-mail goes out. Without a continueUrl the page simply says it is done and the user goes back to the app themselves.
Use your own page instead#
Pass a redirectUrl (one of your link addresses) and the link opens your page with ?token=… instead. Read the token and finish the step with the SDK:
| Link | Call with the token |
|---|---|
| Confirm e-mail | verifyEmail(token) |
| Password reset | resetPassword(token, newPassword) |
Your own page is the way to keep the user inside your app or site from start to end; continueUrl is not used then.
How long the links work#
The confirm link works for 24 hours and the reset link for 30 minutes by default; change them in Email templates. Every link works once. An expired or used link shows "This link can't be used": send a new one (resendVerification, sendEmailVerification or sendPasswordReset).
Safe by design#
- Opening a link changes nothing. The page only shows a button or a form; the work happens when the user presses it. A mail scanner or link preview that opens the link can't use it up.
- The Continue address is checked twice: when the e-mail is sent and again by the page, against your link addresses. Editing the link can't send people to another site.
- Link addresses are compared as addresses, not text: the same scheme, host and port, and a path inside the address.
https://example.comallowshttps://example.com/welcome, neverhttps://example.com.other.net. - The pages run no script and load nothing from elsewhere, can't be put in a frame, and are never cached.
- A reset ends every session of the user, on every device.
Errors#
| Code | When |
|---|---|
| INVALID_INPUT | The redirectUrl or continueUrl is not under one of your link addresses. |
| EMAIL_NOT_VERIFIED | Signing in before the e-mail is confirmed (project requires it): offer resendVerification. |
| TOKEN_INVALID | Your own page sent a token that expired or was already used. |
| RATE_LIMITED | Too many e-mails to one address in a short time. |
Next steps#
- E-mail & Password: sign-up, sign-in, confirmation and reset.
- Ready-made sign-in screen: the whole flow with one call.
- Email templates: the e-mails' language, text and link lifetime.
Last updated: 16 Nov 2026