Resend Contact Verification Email
Resend the contact verification email for a pending verification record.
Throttling
This endpoint enforces strict throttling to prevent abuse:
- Per
verificationId: max 1 resend per 15 minutes - Per reseller account: max 200 resends per rolling hour
nextEligibleAt is always returned so the client knows when it can try again.
On 429, the response uses the standard error envelope, and details contains the earliest retry time (RFC3339 UTC).
Documentation Index
Fetch the complete documentation index at: https://docs.name.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
Authenticate via HTTP Basic with your account username and API token. Examples use an explicit 'Authorization: Basic <base64(username:token)>' header; 'curl -u username:token' is equivalent. For sandbox, append "-test" to your username and use your sandbox token on api.dev.name.com.
Headers
A unique string (e.g., a UUID v4) to make the request idempotent. This key ensures that if the request is retried, the operation will not be performed multiple times. Subsequent requests with the same key will return the original result.
"083910ef-04e4-4bd1-a0bf-3737fe005ca8"
Path Parameters
The verificationId for the pending contact verification record.
Response
Request accepted. An email may have been sent, or the request may be a no-op (for example, if the contact is already verified or there is nothing to send). The sent field indicates whether an email was sent for this request.
Response for resending a contact verification email.
Whether a verification email was sent as a result of this request.
true
The verificationId for the contact verification record.
98752463
When the client can attempt to resend again, as an RFC3339/ISO-8601 UTC timestamp. This field is always returned, including when throttling applies.
"2026-01-14T12:15:00Z"