> ## 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.

# API Key scopes

> validations:email, validations:phone, and validations:cpf scopes for API v1 verification.

<Tip>
  Each scope is a **door** on your key: verify email, phone, or CPF. They are **separate** from send scopes — a list-hygiene key does not need `email:send` or `whatsapp:send`.
</Tip>

## Scopes

| Scope                   | Allows                                       |
| ----------------------- | -------------------------------------------- |
| **`validations:email`** | Verify emails (sync and batch)               |
| **`validations:phone`** | Verify phones (sync and batch)               |
| **`validations:cpf`**   | Look up CPF with birth date (sync and batch) |

Routes covered:

* Email: `POST /v1/validations/email`, `POST /v1/validations/email/batch`, `GET /v1/validations/email/batch/{jobId}`
* Phone: `POST /v1/validations/phone`, `POST /v1/validations/phone/batch`, `GET /v1/validations/phone/batch/{jobId}`
* CPF: `POST /v1/validations/cpf`, `POST /v1/validations/cpf/batch`, `GET /v1/validations/cpf/batch/{jobId}`

<Warning>
  Validation scopes are **independent** from send channels:

  * `validations:email` ≠ `email:send`
  * `validations:phone` ≠ `sms:send` or `whatsapp:send`
</Warning>

## Common combinations

| Flow                               | Scopes                                |
| ---------------------------------- | ------------------------------------- |
| Hygiene email list only            | `validations:email`                   |
| Hygiene phone list only            | `validations:phone`                   |
| CPF lookup on signups only         | `validations:cpf`                     |
| Validate on signup then send email | `validations:email` + `email:send`    |
| Validate WhatsApp then dispatch    | `validations:phone` + `whatsapp:send` |

## Where to configure

1. **Dashboard → Developer → API Keys** — check **Validations → Verify emails**, **Verify phones**, and/or **Look up CPF**
2. **OAuth apps** — include `validations:email`, `validations:phone`, and/or `validations:cpf` in authorized scopes

In the **dashboard** (add-ons), verification uses the user session — it does not consume API Key scopes.

## Next steps

* [Quick Start](/en/validations-api/como-funciona/quick-start)
* [Email validation](/en/validations-api/como-funciona/introducao)
* [Phone validation](/en/validations-api/como-funciona/introducao-telefone)
* [CPF lookup](/en/validations-api/como-funciona/introducao-cpf)