Validating email addresses

Every send to a dead address is a negative signal against your sending domain — bounce rate is a top lever on inbox placement. Validating before you send protects sender reputation: a dead address caught by validation never costs you a bounce.

When to validate:

• before a list's first campaign launch;
• before re-sending to a list older than ~90 days;
• before re-engaging non-responders on lists 6+ months old.

Cost: 1 Data Token = 1 validation result (unknown/error results are free). Check the balance first with account/data_tokens — for a large batch, confirm the balance covers the list size before submitting.

The process

1. Pre-flight the budget — account/data_tokens: compare balance against the number of addresses.
2. Submit — validation/post_emails with emails (raw addresses; unknown ones are created as prospects) and/or prospectIds (already in the CRM). The 202 response is a batch handle, not a result.
3. Poll — validation/batches_by_id with the returned batchId until status is Completed. Validation is asynchronous; expect to poll.
4. Act on results — outcomes are written to each prospect's validation fields (validationStatus, validatedAt). Filter with prospect/get's validationStatus argument — e.g. exclude Invalid/Disposable from the send, keep Valid; treat CatchAll/Unknown per your risk tolerance.

If the balance won't cover the batch

Data Tokens are allotted by plan, can be topped up with add-on packs, and unused tokens roll over for up to 6 months. When the balance is short, say so plainly and direct the user to the plan/billing settings in the Manyreach web app to top up — see How to validate email addresses for the full product walkthrough. Don't submit a batch that will fail midway on budget.