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

# Phone validation

> Check whether a number is valid and has WhatsApp before spending credits on SMS, voice, or WhatsApp.

<Tip>
  **Phone validation** is the **contact list checker**: before calling, sending SMS, or WhatsApp, you know whether the number exists, whether it's mobile or landline, and in full mode whether it **has WhatsApp**. Use the dashboard under **Add-ons → Phone validation** or integrate at signup in your system.
</Tip>

## What is it?

It's an add-on that answers: *is this number usable?*

Unlike [contracting a number](/en/phone-numbers-api/como-funciona/introducao) to **call or send from**, here you **verify customer numbers** in your database — CRM cleanup, forms, or list imports.

## Why use it?

| Without validation                            | With validation                                   |
| --------------------------------------------- | ------------------------------------------------- |
| SMS to 5,000 numbers with 40% invalid         | Remove invalid ones before sending                |
| WhatsApp campaign to a number without the app | In full mode, filter out numbers without WhatsApp |
| Call to landline when you expected mobile     | `line_type` shows mobile, landline, or VoIP       |

## Two verification modes

| Mode                | What it checks                                    | Credits (plan) | Pay as you go |
| ------------------- | ------------------------------------------------- | -------------- | ------------- |
| **Quick** (`quick`) | International format, country, and line type      | 1 per number   | R\$ 0.01      |
| **Full** (`full`)   | Everything in quick + **whether it has WhatsApp** | 27 per number  | R\$ 0.04      |

<Info>
  WhatsApp lookup does **not use Meta's official API** for pre-send checks. The platform runs it internally; you only see the result (`whatsapp_registered`: yes, no, or unknown).
</Info>

## Dashboard vs API

| Channel                                    | Limit                 | Typical use               |
| ------------------------------------------ | --------------------- | ------------------------- |
| **Dashboard** (Add-ons → Phone validation) | Up to **10** numbers  | Manual test, small list   |
| **API** `POST /v1/validations/phone`       | Up to **10** numbers  | Validation at user signup |
| **API** `POST /v1/validations/phone/batch` | **500** to **10,000** | Large lists (async)       |

In the dashboard: paste numbers, choose **Quick** or **Full**, and see results — **approved**, **rejected**, or **unknown**, with **Has WhatsApp** / **No WhatsApp** badges in full mode.

## What each status means

| `status`  | In plain English                                               |
| --------- | -------------------------------------------------------------- |
| `valid`   | Valid number (and with WhatsApp in full mode, when applicable) |
| `invalid` | Invalid format or no WhatsApp (full mode)                      |
| `unknown` | Format OK, but full verification could not complete            |
| `risky`   | Low-confidence signals (when applicable)                       |

Useful fields per item:

| Field                 | What it is                                           |
| --------------------- | ---------------------------------------------------- |
| `phone`               | Normalized number (e.g. `+5511999999999`)            |
| `phone_valid`         | Passed format check                                  |
| `line_type`           | `mobile`, `fixed_line` (landline), `voip`, or `null` |
| `country_code`        | Country (e.g. `BR`)                                  |
| `whatsapp_registered` | `true` / `false` in full mode; `null` in quick mode  |
| `reason`              | Human-readable text for logs or tooltips             |
| `credits_charged`     | Credits charged for this check                       |

## Shared pool (optional)

Workspaces with an unofficial WhatsApp line can opt in under **Workspace settings → Phone validation assistance** to contribute lines to a shared pool. **Off by default.** Your own checks always use your workspace lines first.

## API Key scope

Phone routes require **`validations:phone`** — separate from `sms:send`, `whatsapp:send`, and `validations:email`.

## 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)
* [Email validation](/en/validations-api/como-funciona/introducao)
* [CPF lookup](/en/validations-api/como-funciona/introducao-cpf)
* [Pricing API](/en/guides/precos/api-de-precos) — SKUs `PHONE_VERIFY_QUICK` and `PHONE_VERIFY_FULL`