Verify Player Email
horizon_verify_emailVerifies a player's email using the single-use token from their registration email, consumes it, and marks the email verified so the player can proceed to sign in.
Instructions
Verifies a player's email using the single-use token from their registration email. Use when: the player follows the verification email and explicitly requests completion. Not for: password reset tokens (use horizon_reset_password) or creating accounts (use horizon_signup_email). Side effects: consumes the verification token and marks the email verified. It does not sign in. Returns: empty HTTP 200 represented as null; then use horizon_signin_email. Errors: 400 for an invalid or expired verification token; request a fresh verification email through the approved account support flow. Needs HORIZON_API_KEY. Every failure returns an error result (isError) with the HTTP status and body: a 401 that horizon_test_connection also returns means HORIZON_API_KEY is wrong, 429 means the account's per-minute rate limit was reached (wait a minute, then retry).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"token": "<token>"
},
"name": "horizon_verify_email"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes | Single-use token from the player's verification or password-reset email (max 256 characters) |