---
title: "Email confirmation page (browser-facing)"
method: GET
path: "/v1/agent/verify-email"
---

# Email confirmation page (browser-facing)

`GET /v1/agent/verify-email`

## Request

- Base URL: `https://api.myotp.app`
- URL: `https://api.myotp.app/v1/agent/verify-email`
- Auth: none declared

Browser-facing, not for agents. This is the link in the confirmation email. It renders an HTML page with a Confirm button; the human presses it and the page POSTs the token back. The token is single use and valid for 24 hours. An agent cannot complete this step; it should tell the human to open the email and poll GET /v1/agent/account for email_verified instead.

## Query parameters

- `token` string, required

## Response `200`

The confirmation page.

## Other responses

- `429`: Too many requests from this IP address. The edge allows 100 requests a minute per client IP with a burst of 100, counted across every endpoint together, so sends and status checks share one budget. Accounts that ask for more are raised to 500 a minute; X-RateLimit-Limit on every response tells you which ceiling applies to you. Wait the number of seconds in Retry-After and repeat the request. Write to support@myotp.app with the addresses you call from and the peak you are designing for if you need a higher limit.

---

[API](https://skmtc.dev/myotp/apis/myotpapp-api.md) · [All operations](https://skmtc.dev/myotp/apis/myotpapp-api/llms.txt) · [OpenAPI document](https://skmtc.dev/myotp/apis/myotpapp-api/revisions/95ed911fdece?raw)
