Sign in

v1

latestOpenAPI 3.1.02026-07-2671111437.2 KB
Contact Verification

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

post/core/v1/contacts/verify/{verificationId}:resend

Path parameters

verificationIdinteger required

The verificationId for the pending contact verification record.

Headers

X-Idempotency-Keystring
Example:083910ef-04e4-4bd1-a0bf-3737fe005ca8

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.

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.

sentboolean required

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

verificationIdinteger required

The verificationId for the contact verification record.

nextEligibleAtstring 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 response

{
  "sent": true,
  "verificationId": 98752463,
  "nextEligibleAt": "2026-01-14T12:15:00Z"
}