---
title: "Verify email from browser link click"
method: GET
path: "/api/auth/email/verify-link"
tags: ["Client"]
---

# Verify email from browser link click

`GET /api/auth/email/verify-link`

Browser-oriented link verification flow.

This endpoint is intended for users clicking verification links in email.
It validates the token on the backend and redirects the browser to the
stored, validated `redirectTo` URL with the verification result.

Redirect query params:
- Success: `insforge_status=success&insforge_type=verify_email`
- Error: `insforge_status=error&insforge_type=verify_email&insforge_error=...`
- `insforge_status`: `success` or `error`
- `insforge_type`: always `verify_email`
- `insforge_error`: present only on error, human-readable message

Recommended handling: use your sign-in page as `redirectTo`. When the
redirect arrives with `insforge_status=success`, show a confirmation message
and ask the user to sign in with their email and password.

## Query parameters

- `token` string, required

## Other responses

- `302` — Browser redirected to the stored redirect URL
- `400` — Invalid verification token or redirect target

---

[API](https://skmtc.net/insforge/apis/insforge-authentication-api.md) · [All operations](https://skmtc.net/insforge/apis/insforge-authentication-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/insforge/insforge-authentication-api/versions/a935bb49f932/schema)