Email verification often starts as one column and one endpoint: store a token, set verified = true when the token arrives, and return success. That works until users click an old link, a mobile client retries after a timeout, or two requests redeem the same token at nearly the same time.
The durable approach is to model verification as a small state machine. The API then reports what happened instead of making clients infer state from a boolean or from inconsistent error messages. This also makes email fixtures, including a free disposable email address or a temp mail generator used in test environments, easier to reason about without weakening production rules.
Why a boolean verified flag is not enough
A boolean answers only one question: has this account been verified at some point? It cannot explain whether a token was issued, consumed, expired, revoked, or rejected because it belongs to another account.
Those distinctions matter for both security and operations.…