Send the verification email to an email address

POST /v1/users/{user_id}/emails/{email_id}:send-verification · permission users:write

Sends the verification email to one email row of the user. email_id is the internal UUID (lowercase, hyphenated). The response carries the expiry of the verification request; no code or link is returned. The optional body only selects the email language.

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

Optional body:

Field Type Required Description
locale string no BCP 47 language tag of the email, for example tr or pt-BR. Defaults to the user's or the environment's language.

Response

200 OK. expires_at is when the verification request expires.

{
  "expires_at": "2026-01-16T09: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 has an unknown field.
409 conflict The email is already verified.
415 unsupported_media_type A body was sent without Content-Type: application/json.
422 validation_failed locale is not a valid BCP 47 language tag, or a field has the wrong type.
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 API rate limit or the per-user email sending 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:send-verification \
  -H "Authorization: Bearer $KEENAUTH_SECRET_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"locale": "en"}'

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.