> ## 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. # 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). ## OpenAPI ````yaml post /core/v1/contacts/verify/{verificationId}:resend openapi: 3.1.0 info: contact: email: reseller@name.com name: Reseller Account Services description: >- RESTful API for managing domains, DNS records, and related services at name.com. Access via HTTPS at api.name.com (production) or api.dev.name.com (testing). Supports standard authentication, rate-limited to 20 requests/second. title: name.com Core API version: 1.29.4 termsOfService: https://www.name.com/policies/api-access-agreement servers: - description: Testing url: https://api.dev.name.com security: - BasicAuth: [] tags: - name: Hello description: >- Use the Hello endpoint to verify that your API connection and credentials are working properly. This simple call returns a success message (along with server time and version info) to confirm the API is reachable and authenticated. - name: Account Info description: >- Use Account Info endpoints to retrieve basic information about your name.com account. For example, you can check your account’s current credit balance and other account details using these endpoints. - name: Accounts description: >- Use Accounts endpoints (available upon request) to manage sub-accounts under your main account. For example, resellers can programmatically create new customer accounts with their own login credentials and permissions. - name: Domains description: >- Use Domains endpoints to search for domain availability, register new domains, and manage existing domains. - name: Contact Verification description: >- Use Contact Verification endpoints to query a reseller’s unverified domains/emails and to programmatically mark an end user’s email as verified if the reseller has already completed the verification process. These endpoints help resellers meet ICANN requirements by ensuring end users confirm they can receive email at their listed address. - name: DNS description: >- Use DNS endpoints to manage DNS records for your domains. You can list all existing DNS records for a domain and create, update, or delete records as needed. - name: DNSSECs description: >- Use DNSSEC endpoints to configure DNS Security Extensions for your domains. These endpoints allow you to add, retrieve, or remove DNSSEC records. - name: Email Forwardings description: >- Use Email Forwardings endpoints to set up and manage email forwarding addresses on your domains. - name: URL Forwardings description: >- Use URL Forwardings endpoints to control URL redirection settings for your domains. - name: Vanity Nameservers description: >- Use Vanity Nameservers endpoints to configure custom nameserver hostnames (glue records) for your domains. - name: Transfers description: >- Use Transfers endpoints to move domains into your name.com account. Start by creating a transfer request for inbound transfers from **external** registrars, then monitor and manage the status of pending transfers. Use **internal transfer in** to pull a domain from another name.com account into your reseller account (enterprise allowlist; requires auth code from the losing account’s dashboard). You can cancel an incoming transfer if needed, or cancel an outbound transfer (domain leaving name.com) via the external transfer-out cancel endpoint. Use the **transfer eligibility** endpoint to check whether a domain is currently at name.com before initiating a transfer, so you can route to the correct flow (external vs internal transfer). - name: Orders description: Use Orders endpoints to review and track purchases made via the API. - name: Refunds description: > Use the Refunds endpoint to delete eligible domains and advanced security products during the Add Grace Period (AGP) and automatically issue refunds for the associated order items. You can use the List Orders endpoint to retrieve order IDs, then pass those IDs into the Refunds endpoint to process eligible deletions and refunds. This endpoint enforces AGP delete limits and supports only domain registrations and advanced security add-ons. Refunds are issued to the original payment method on file. If the original payment method is unavailable, the refund will be credited to the account balance. - name: Webhook Notifications description: > Use Webhook Notification endpoints to subscribe to real-time notifications for account and domain events. This keeps your application updated on important changes without polling the API. Outbound webhook POSTs include an `X-NAMECOM-SIGNATURE` header. HMAC uses one API v4 token per account, chosen deterministically when multiple tokens exist (see HMAC Signature Verification in the developer docs). The signing input format is unchanged. - name: Domain Info description: >- Use Domain Info endpoints to retrieve information about TLD-specific requirements and registration rules. These endpoints help you understand what fields, documents, or constraints are needed to successfully register domains across different TLDs. - name: TLD Pricing description: >- Use TLD Pricing endpoints to retrieve general pricing information for your account. - name: Premium Domains description: APIs for working with Premium Domains. paths: /core/v1/contacts/verify/{verificationId}:resend: post: tags: - Contact Verification summary: Resend Contact Verification Email description: >- 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). operationId: ResendContactVerificationEmail parameters: - description: The verificationId for the pending contact verification record. in: path name: verificationId schema: type: integer format: int32 required: true example: 98752463 - name: X-Idempotency-Key in: header description: >- 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. schema: type: string example: 083910ef-04e4-4bd1-a0bf-3737fe005ca8 required: false responses: '200': description: >- 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. content: application/json: schema: $ref: '#/components/schemas/ContactVerificationResendResponse' examples: sent: summary: Email sent value: sent: true verificationId: 98752463 nextEligibleAt: '2026-01-14T12:15:00Z' noop: summary: No-op (already verified / nothing to send) value: sent: false verificationId: 98752463 nextEligibleAt: '2026-01-14T12:00:00Z' '401': description: Unauthorized. content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error example: Unauthorized '403': description: Forbidden - you do not have permission to perform this action. content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error example: Permission denied details: type: - string - 'null' description: Additional context or information about the error example: Failed authentication '404': description: >- The submitted verificationId was not found or is not associated with this account. content: application/json: schema: $ref: '#/components/schemas/NotFound404' '405': description: Method not allowed. content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error example: Method Not Allowed '409': description: >- When sending idempotent requests, this response indicates that there was an issue with the idempotency keys. content: application/json: schema: type: object properties: message: type: string example: Idempotency key has been reused for a different request. '415': description: >- All POST, PUT, PATCH requests for this API must include the `Content-Type: application/json` header in the requests. content: application/json: schema: $ref: '#/components/schemas/UnsupportedMedia415' '429': description: >- Throttled. The response uses the standard error envelope; `details` contains the earliest retry time (RFC3339 UTC). content: application/json: schema: type: object required: - message - details properties: message: type: string description: >- A human-readable message providing more details about the error. example: Resend throttled details: type: string description: Earliest retry time (RFC3339 UTC). example: 'Next eligible at: 2026-01-20T21:49:58+00:00' examples: throttled: summary: Throttled value: message: Resend throttled details: 'Next eligible at: 2026-01-20T21:49:58+00:00' headers: x-ratelimit-reset: description: >- Unix timestamp for the time at which the current rate limit will reset. schema: type: number example: 1747668270 '500': description: Internal server error. content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error. example: Internal Server Error details: type: - string - 'null' description: Additional context or information about the error. example: Something went wrong. '502': description: Bad Gateway content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error. example: >- The server received an invalid response from the upstream server. '504': description: Gateway Timeout content: application/json: schema: type: object required: - message properties: message: type: string description: >- A human-readable message providing more details about the error. example: The upstream server is taking too long to respond. components: schemas: ContactVerificationResendResponse: description: Response for resending a contact verification email. type: object properties: sent: type: boolean description: Whether a verification email was sent as a result of this request. example: true verificationId: type: integer format: int32 description: The verificationId for the contact verification record. example: 98752463 nextEligibleAt: type: string format: date-time description: >- 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' required: - sent - verificationId - nextEligibleAt NotFound404: type: object required: - message properties: message: type: string description: A human-readable message providing more details about the error example: Not Found details: type: - string - 'null' description: Additional context or information about the error example: The requested domain does not exist. UnsupportedMedia415: type: object required: - message properties: message: type: string description: A human-readable message providing more details about the error example: >- The 'Content-Type' header must be 'application/json' for this request. securitySchemes: BasicAuth: scheme: basic type: http description: >- Authenticate via HTTP Basic with your account username and API token. Examples use an explicit 'Authorization: Basic ' header; 'curl -u username:token' is equivalent. For sandbox, append "-test" to your username and use your sandbox token on api.dev.name.com. ````