> ## Documentation Index
> Fetch the complete documentation index at: https://docs.notifique.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Email validation

> Check whether an email exists and can receive messages before spending credits on campaigns.

<Tip>
  **Email validation** is the **filter before sending**: like checking the address on an envelope before mailing a letter — it avoids bounces, dirty lists, and credits spent on destinations that don't exist. Use the dashboard under **Add-ons → Email validation** or integrate at signup in your system.
</Tip>

## What is it?

It's an add-on that answers a simple question: *is this email deliverable?*

You send a list (up to 10 in the dashboard or sync API, up to 10,000 in batch) and get, for each address, whether it passed or not — with the reason when it fails.

## Why use it?

| Without validation                             | With validation                        |
| ---------------------------------------------- | -------------------------------------- |
| Campaign to 10,000 emails with 30% invalid     | Remove invalid ones **before** sending |
| High bounce rate and domain reputation drops   | Clean list, fewer rejections           |
| Credits spent on destinations that don't exist | Pay only for what you verify           |

## Two verification modes

| Mode                | What it checks                                 | Credits (plan) | Pay as you go |
| ------------------- | ---------------------------------------------- | -------------- | ------------- |
| **Quick** (`quick`) | Format, disposable domain, and MX record       | 1 per email    | R\$ 0.01      |
| **Full** (`full`)   | Everything in quick + whether the inbox exists | 5 per email    | R\$ 0.01      |

<Info>
  Use **quick** to clean large lists at low cost. Use **full** when delivery depends on the address being real (e.g. before OTP or critical transactional).
</Info>

## Dashboard vs API

| Channel                                    | Limit               | Typical use                     |
| ------------------------------------------ | ------------------- | ------------------------------- |
| **Dashboard** (Add-ons → Email validation) | Up to **10** emails | Manual test, small list         |
| **API** `POST /v1/validations/email`       | Up to **10** emails | Real-time integration at signup |
| **API** `POST /v1/validations/email/batch` | Up to **10,000**    | Large lists (async processing)  |

In the dashboard: paste emails (one per line or comma-separated), choose **Quick** or **Full**, and see results on the right — **approved**, **rejected**, **risky**, or **unknown**.

## What each status means

| `status`  | In plain English                                                                 |
| --------- | -------------------------------------------------------------------------------- |
| `valid`   | Looks deliverable — safe to send                                                 |
| `invalid` | Invalid — wrong format, missing MX, disposable, or rejected in full verification |
| `risky`   | Risky — catch-all or low-confidence signals                                      |
| `unknown` | Could not conclude — try full mode or batch                                      |

Useful fields in the response: `disposable` (temporary email), `mx_found` (domain accepts email), `catch_all`, `suggested_spelling` (suggested correction), `credits_charged`.

## API Key scope

Email routes require **`validations:email`** — separate from `email:send` (sending messages).

## Also available: phone validation and CPF lookup

Need to check numbers and WhatsApp before sending? See [Phone validation](/en/validations-api/como-funciona/introducao-telefone).

For Brazilian document signups, use [CPF lookup](/en/validations-api/como-funciona/introducao-cpf).

## Next steps

* [Quick Start](/en/validations-api/como-funciona/quick-start)
* [Modes and billing](/en/validations-api/como-funciona/modos-e-cobranca)
* [API Key scopes](/en/validations-api/como-funciona/escopos-da-api-key)
* [Pricing API](/en/guides/precos/api-de-precos) — SKUs `EMAIL_VERIFY_QUICK` and `EMAIL_VERIFY_FULL`