Sign in
email-verification

GET `/api/v0/main-frontend/email-verification/status` - Whether the signed-in account's address is proven, and what we last mailed about it.

Changed on
get/api/v0/main-frontend/email-verification/status

Request

  • The document declares no server URL.
  • Auth: none declared

Response

Email verification status of the signed-in user

emailstring required
email_verified_atstring date-time nullable
email_verified_method'emailed_code' | 'password_reset_backfill' | 'tmc_confirmed' | 'admin_asserted'

How proof of control over [UserDetail::email] was obtained. AdminAsserted is the weakest.

template_configuredboolean required

False when verification_enabled but the deployment has no verify_email_address template: requesting a code would 500, so the frontend hides the feature instead.

verification_enabledboolean required

False switches the feature off entirely; the request and verify endpoints 404 then.

Changes