Skip to main content
POST
/
core
/
v1
/
contacts
/
verify
/
{verificationId}
:resend
Resend Contact Verification Email
curl --request POST \
  --url https://api.dev.name.com/core/v1/contacts/verify/{verificationId}:resend \
  --header 'Authorization: Basic <encoded-value>'
{
  "sent": true,
  "verificationId": 98752463,
  "nextEligibleAt": "2026-01-14T12:15:00Z"
}

Authorizations

​
Authorization
string
header
required

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

​
X-Idempotency-Key
string

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.

Example:

"083910ef-04e4-4bd1-a0bf-3737fe005ca8"

Path Parameters

​
verificationId
integer<int32>
required

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.

​
sent
boolean
required

Whether a verification email was sent as a result of this request.

Example:

true

​
verificationId
integer<int32>
required

The verificationId for the contact verification record.

Example:

98752463

​
nextEligibleAt
string<date-time>
required

When the client can attempt to resend again, as an RFC3339/ISO-8601 UTC timestamp. This field is always returned, including when throttling applies.

Example:

"2026-01-14T12:15:00Z"