> ## Documentation Index
> Fetch the complete documentation index at: https://docs.insforge.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Verify email from browser link click

> 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.




## OpenAPI

````yaml https://raw.githubusercontent.com/InsForge/InsForge/main/openapi/auth.yaml get /api/auth/email/verify-link
openapi: 3.0.3
info:
  title: Insforge Authentication API
  version: 2.0.0
  description: Authentication endpoints with separated auth and profile tables
servers: []
security: []
paths:
  /api/auth/email/verify-link:
    get:
      tags:
        - Client
      summary: Verify email from browser link click
      description: >
        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.
      parameters:
        - name: token
          in: query
          required: true
          schema:
            type: string
          description: 64-character email verification token from the email link
      responses:
        '302':
          description: Browser redirected to the stored redirect URL
        '400':
          description: Invalid verification token or redirect target

````