> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/adding-questions-and-content/question-reference/email-address.md).

# Email address

Collects email addresses.

This question type is commonly used for collecting and validating email addresses from responders. 

## Data structure

The answer to the email question is stored as [Formsort subtype](/response-data-collection-and-management/variable-schema.md#subtypes) email . 

```
{
  "my_email": "hello@formsort.com"
}
```

## **Suggesting spelling corrections**

Beyond validating for email structure itself, when **Warn about common domain typos** is enabled, Formsort suggests potential corrections to non-standard domains.

For example, an answer ending like *gnail.com* would be met with a prompt asking if the responder meant *gmail.com,* and the responder would be prompted to correct it before continuing.

![A warning about an email type](https://1036686854-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJPnL__mOdr_mLZ8nwf%2F-MKpA2ZRsJl-FlArhxQz%2F-MKpAyz8EOM0vbj83wym%2Fimage.png?alt=media\&token=748a81df-1da4-4c54-a2c9-c127a7167310)

{% hint style="info" %}
Warnings about common domain typos work best when responders are consumers using common email providers. If your responders are using business emails you may want to disable this feature.
{% endhint %}

## **Allowing multiple answers**

Enabling **Allow multiple answers** lets the respondent type more than one email address as an answer to your question. 


---

# 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.formsort.com/adding-questions-and-content/question-reference/email-address.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.