Mark an email address as verified by an administrator

POST /v1/users/{user_id}/emails/{email_id}:verify · permission users:write

Marks the address as verified on your authority. No code or link is sent to the user, and the verification method is stored as admin_api, so it is not proof that the user controls the mailbox; prefer :send-verification when you have not verified the address yourself. If the address is already verified nothing is written and 200 is returned. Unverified copies of the same address on other accounts of the environment are removed. The change is written to the management audit log as user.email_verified with the API key as actor, and emits user.updated.

Request

Parameter In Required Description
user_id path yes User id, prefixed usr_.
email_id path yes Id of the email row (internal UUID, lowercase, hyphenated), as returned by GET /v1/users/{user_id}/emails.

The request takes no body (an empty body or {} is accepted).

Response

200 OK with the updated email row. Without the users:read_pii permission the address is masked (a***@e***.com).

{
  "id": "0191f0a0-3333-7444-8555-666666666666",
  "email": "ada@example.com",
  "verified": true,
  "primary": false,
  "created_at": "2026-01-15T09:30:00Z"
}

Errors

Every error is an application/problem+json body with a stable code.

HTTP code When
400 malformed_request, unknown_field The body is not valid JSON, or is neither empty nor {}.
404 not_found The user or the email row does not exist in this environment, the email does not belong to this user, or an id is malformed.
401 unauthenticated The API key is missing, invalid or revoked.
403 insufficient_permissions The key lacks the users:write permission.
429 rate_limited The rate limit was exceeded; honor Retry-After.
503 service_unavailable A dependency is temporarily unavailable; retry later.

Example

curl -X POST https://api.eu.keenauth.com/v1/users/usr_0a1b2c3d4e5f6g7h8j9k0m1n2p/emails/0191f0a0-3333-7444-8555-666666666666:verify \
  -H "Authorization: Bearer $KEENAUTH_SECRET_KEY"

Personal data

This endpoint carries personal data: end-user profile. Personal data in the KeenAuth APIs describes what is stored, how long it is kept and how it is deleted. Do not send special categories of personal data (health, biometric data, religion, political opinions, sexual orientation) in any field.