> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/form-designer/answers/answer-types/email-validator.md).

# Email Validator

The email validator answer type will validate the email entered by the respondent using a unique code that will be sent to the respondent and which is required to submit the survey if the email validator field has been set as required.

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MByFFXE_7Eur7Q8j56m%2F-MBz5KOYtrlml2_2C1XK%2Fimage.png?alt=media\&token=f5539fdb-bc08-4181-bed4-1b7acf4f0dce)

## 🔅Email Validator properties

You may configure additional email validator properties from the [answer properties](/form-management/form-designer/answers/answer-properties.md) page.

* **`From name`** confirmation email sender name.
* **`From email`** confirmation email sender.
* **`Subject`** confirmation email's subject. 
* **`Confirmation body`** confirmation email message body. The {**0}** tag is replaced at runtime by the validation code. 
* **`Expires after`** minutes after which  the authorization of the confirmation validation is not valid anymore and requires the respondent to re-confirm.

{% hint style="info" %}
In [multi-language](/form-management/form-designer/multi-language-forms.md) surveys you can define different properties for each of your language. To set the properties for a given language select the edition language in the designer and then update the properties.  
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ngsurvey.com/form-management/form-designer/answers/answer-types/email-validator.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.