Resend an identity-confirmation email
POST
/verification-resends
email-password auth method that has not yet been verified. Use this when the original confirmation email sent at registration expired, was lost, or never arrived.identity-confirmation token is generated and the previous one is invalidated — only the most recently issued code will verify successfully. Email delivery is asynchronous: a successful 200 response only confirms the resend was accepted, not that the email has been delivered.200/{ "pending": true } result regardless of whether the email address belongs to a real account, whether that account is an email-password auth method, or whether it has already been verified — no information about account existence or verification state is ever leaked through the response.429/403 response when the target account genuinely exists and is unverified — unknown or already-verified emails always receive the generic 200. Requests are also rate-limited per source IP address, independently of the target email and regardless of whether it belongs to a real account: at most 20 resend requests per calling IP within a rolling 1-hour window, to guard against enumeration/scanning across many different addresses.email in the request body.Request
Body Params application/jsonRequired
Responses
Request Request Example
Shell
JavaScript
Java
Swift
curl --location '/verification-resends' \
--header 'Content-Type: application/json' \
--data-raw '{
"email": "ada@example.com"
}'Response Response Example
200 - Success
{
"message": "Resend request accepted",
"status": "success",
"data": {
"pending": true
}
}Modified at 2026-09-30 00:29:30