Verification
Free basic checks on every address, and paid deep verification of your contacts before you send.
Verification keeps mail away from addresses that will bounce, which protects your deliverability. There are two levels.
Basic checks (free, all plans)
BillionSend checks the recipient’s domain whenever an email is accepted and whenever a contact is created or imported. It refuses an address when:
- the domain is a reserved or documentation name (
.test,.invalid,example.comand similar) or is not a real top-level domain, - the domain has no mail server: it does not exist, or it publishes no MX record (or a null MX),
- the domain belongs to a disposable email service.
A refused send or contact returns 422 validation_error with a message such as x@example.com can never receive mail: …. In a bulk import, those rows are skipped. Nothing is billed. To test sending without emailing anyone, use success@simulator.amazonses.com.
Deep verification (paid plans)
Deep verification checks whether each mailbox exists, without sending anything to it. It costs $0.40 per 1,000 addresses, billed with your monthly invoice (nothing to prepay), and it is available on Starter, Pro and Scale. On Free, the Verify buttons are disabled and only basic checks apply.
It works only on the contacts in your team. If your team has free verification credit, it is used before anything is billed.
Start a verification
In the dashboard, you can start it from:
- Audience → Contacts: select contacts, then press Verify.
- A segment page: press Verify to check all of its members.
- The import dialog: tick Verify after import to check the new contacts.
- A broadcast’s “Before you send” panel: it shows how many recipients were never verified and offers Verify now.
Before it starts, the dialog shows how many addresses will be checked and what they cost. Owners, admins and marketing members can start it. See Team roles.
Results
Each contact gets a verdict, shown in the Verification column and on the contact’s page:
| Verdict | Meaning |
|---|---|
valid |
The mailbox exists. |
invalid |
The mailbox does not exist. |
risky |
It may bounce. |
catchall |
The domain accepts every address, so the mailbox cannot be confirmed. |
role |
A shared address such as info@ or support@. |
disposable |
A throwaway mailbox. |
unknown |
No answer could be obtained. |
An invalid address is added to your suppression list automatically, so no email reaches it. The other verdicts only label the contact; the contact stays in your list and still gets mail.
What is billed
- You pay for results only: addresses that end
unknownare not billed, and a run that fails is not billed. - A contact that already has a result is skipped, and so is a contact that is being verified in another run. No address is billed twice.
- Settings → Billing and usage shows this month’s verified addresses and cost, and your recent runs.
Limits
| Contacts per start | 500,000. For a larger list, verify by segment in parts. |
| Contacts per run | 50,000. A bigger start is split into several runs. |
| Time for a run | 12 hours. A run that is not done by then fails. |
API
Everything the dashboard does is in the API too. A target is { "kind": "contacts", "contact_ids": [...] }, { "kind": "segment", "segment_id": "..." } or { "kind": "broadcast", "broadcast_id": "..." }.
| Request | What it does |
|---|---|
GET /verifications/availability |
Whether your team can start deep verification, and the price per 1,000 addresses. |
POST /verifications/estimate |
How many contacts of a target were never verified and what verifying them costs. Changes nothing. |
POST /verifications |
Starts verifying a target. Add "recheck": true to verify contacts that were verified before. |
GET /verifications |
Your runs, newest first, with their status and results. |
GET /verifications/{id} |
One run. |
curl -X POST https://api.billionsend.com/verifications \
-H "Authorization: Bearer bs_..." \
-H "Content-Type: application/json" \
-d '{ "target": { "kind": "segment", "segment_id": "seg_id" } }'
Each contact’s result is on the contact: GET /contacts/{id} and GET /contacts return verification_status (valid, invalid, risky, catchall, role, disposable or unknown) and verified_at, both null until the contact is verified. GET /usage shows this month’s verified addresses and cost under verification. Starting a run needs a key with full access; on the Free plan it answers 403 plan_limit_reached. The MCP server has the same five actions (see MCP).