---
title: "Verify Email"
method: GET
path: "/v1/auth/verify"
---

# Verify Email

`GET /v1/auth/verify`

## Request

- Base URL: `https://api.quantradin.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.quantradin.com/v1/auth/verify`
- Auth: none declared

Verify an email via the link in the verification message.  Idempotent: a
fresh token verifies the account; clicking the SAME link again (already-used
token, user already verified) still lands on the success page rather than an
error.  Redirects to the web app with ?verified=1 (ok) or ?verified=0
(expired/unknown link — the app shows a resend prompt).

Side effect: on the FIRST successful verify, the post-verification welcome
email is scheduled via BackgroundTasks (best-effort, off the request path).
The send is gated by a compare-and-set on welcomed_at (_enqueue_welcome_once
-> db.claim_welcome), so a double-click / re-verify never sends a second
welcome, and a mail failure never breaks verification.

## Query parameters

- `token` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/quantradin/apis/vega-api.md) · [All operations](https://skmtc.dev/quantradin/apis/vega-api/llms.txt) · [OpenAPI document](https://skmtc.dev/quantradin/apis/vega-api/revisions/47add154ef38?raw)