---
title: "Resend Contact Verification Email"
method: POST
path: "/core/v1/contacts/verify/{verificationId}:resend"
tags: ["Contact Verification"]
---

# Resend Contact Verification Email

`POST /core/v1/contacts/verify/{verificationId}:resend`

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

## Path parameters

- `verificationId` integer, required

## Headers

- `X-Idempotency-Key` string

## Response `200`

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.

- ContactVerificationResendResponse — Response for resending a contact verification email.
  - `sent` boolean, required — Whether a verification email was sent as a result of this request.
  - `verificationId` integer, required — The verificationId for the contact verification record.
  - `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.

## Other responses

- `401` — Unauthorized.
- `403` — Forbidden - you do not have permission to perform this action.
- `404` — The submitted verificationId was not found or is not associated with this account.
- `405` — Method not allowed.
- `409` — When sending idempotent requests, this response indicates that there was an issue with the idempotency keys.
- `415` — All POST, PUT, PATCH requests for this API must include the `Content-Type: application/json` header in the requests.
- `429` — Throttled. The response uses the standard error envelope; `details` contains the earliest retry time (RFC3339 UTC).
- `500` — Internal server error.
- `502` — Bad Gateway
- `504` — Gateway Timeout

---

[API](https://skmtc.dev/name/apis/name-com-core-api.md) · [All operations](https://skmtc.dev/name/apis/name-com-core-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/name/name-com-core-api/revisions/a37d4cbd3991/schema)