# 12 Domains API: Restart gTLD email verification

*This is a series of articles in which we are going to cover registrant contact verification.*

*This is a third article in a series in which we are going to restart email verification procedure for a gTLD domain owner. Navigate [here](https://openprovider.help/books/api-plugins/page/10-domains-api-check-gtld-email-verification-status) to go back to the first article. To get more information about our API in general, please use our [documentation portal](https://docs.openprovider.com) as your reference.*

Due to ICANN requirements, Openprovider is obliged to verify the validity of each email address that is used in the owner contact details of any gTLD registration. gTLDs include all extensions that are not country codes (ccTLDs): common generics like .com, .net and .travel, and all new gTLDs like .guru, .berlin and .app.

Usually, this process is handled automatically depending on the actions that are being applied to a domain. More on this could be found in our [Knowledge Base.](https://openprovider.help/books/domains/page/registrant-email-verification-icann-contact-validation) However, if for some reason the process should be re-initiated, we have corresponding API methods for the very same purpose.

## <span>Restarting validation</span>

One should use R<span>estart Email Verification method i</span>n order to restartvalidation of an owner's email address.

***NB** Executing this command during an already running email validation process will cause resending of the last verification email to a customer*

<div id="bkmrk-use-endpoint-path-be">![Entering Geo Fence icon](https://openprovider.help/uploads/images/gallery/2026-08/embedded-image-yebbdriq.png)Use endpoint path below. Base URL is determined by both the target environment and API version.</div><div id="bkmrk-get-%7Bbase_url%7D%2Fcusto">```
<span><strong>GET</strong> <a href="http://docs.openprovider.com/#operation/"><strong>{base_url}</strong></a>/customers/verifications/emails/start</span>
```

</div><div id="bkmrk-request-values-name-"><details><summary>REQUEST VALUES</summary>

<table><tbody><tr><td>**<span>Name</span>**</td><td>**<span>Type</span>**</td><td>**<span>Description</span>**</td></tr><tr><td>email</td><td>string</td><td>**Required.**</td></tr></tbody></table>

</details>  
<div id="bkmrk-request-examplecurl-"><div><details><summary>REQUEST EXAMPLE</summary>

```
curl -X POST \<br></br> https://api.openprovider.eu/v1beta/customers/verifications/emails/restart \<br></br> -H 'Authorization: ' \<br></br> -H 'Content-Type: application/json' \<br></br> -d '{<br></br> "email": "email@domain.com",<br></br> "handle": "XX123456-XX",<br></br> "language": "en"<br></br>}'
```

</details></div><details><summary>RESPONSE EXAMPLE</summary>

```
{<br></br>"code": 0,<br></br>"data": {<br></br>"success": true<br></br>},<br></br>"desc": ""<br></br>}
```

</details>### RESPONSE VALUES

If the operation went successfully, one will receive a corresponding code (0).

</div></div>