Expand description
Handlers for HTTP requests to /api/v0/main-frontend/email-verification.
Proving that an account can read the address it claims: user_details.email is self-service editable,
and the OIDC discovery document advertises an email_verified claim.
Structs§
- Email
Verification Email Info - What we last mailed about the address the account holds now. Never a delivery confirmation: we hand messages to an SMTP relay and cannot see an inbox.
- Email
Verification Status - Main
Frontend 🔒Email Verification ApiDoc - Request
Email Verification Payload - Verify
Email Ownership Payload
Enums§
- Request
Email Verification Outcome - Verify
Email Ownership Result - Outcome of submitting a code. Wrong, expired, superseded and spent are one value: they are indistinguishable to someone typing digits, and telling them apart only helps a guesser.
Constants§
- PURPOSE 🔒
Functions§
- _add_
routes - get_
email_ verification_ code_ for_ test_ mode - GET
/api/v0/main-frontend/email-verification/test-mode-code- The signed-in account’s own pending verification code. - get_
my_ email_ verification_ status - GET
/api/v0/main-frontend/email-verification/status- Whether the signed-in account’s address is proven, and what we last mailed about it. - request_
email_ verification_ code - POST
/api/v0/main-frontend/email-verification/request- Mails a fresh verification code to the signed-in account’s current address. - verify_
email_ ownership - POST
/api/v0/main-frontend/email-verification/verify- Spends a mailed code and records the proof.