validation/post_emails

Tool: create

Submit emails or existing prospects for asynchronous email validation.

Validate to protect sender reputation — a dead address caught here never costs a bounce; do it before a first launch, a resend to a list older than ~90 days, or a 6+ month re-engagement. Full recipe: guides/validating-emails.

Raw emails not yet in the CRM are created as prospects first, then queued. The 202 response is a batch handle, not a result — poll validation/batches_by_id with the returned batchId; results are written to each prospect's validation fields when processing completes. Recently-validated and duplicate items are skipped before queueing (reported in skipped). Validation spends Data Tokens: estimatedMaxDataTokens is the ceiling for the batch, and unknown/error results are free.

Provide emails, prospectIds, or both. Both fields are optional individually — an empty request queues nothing.

Body

field	type	req	constraints	description
emails	array	–		Email addresses to validate. Missing emails are created as CRM prospects before validation.
prospectIds	array	–		Existing prospect IDs to validate (int64), when you already store Manyreach prospect ids.

Response

202 — Validation batch accepted.

field	type	description
mode	string	Processing mode; currently always async.
batchId	string	Batch id (uuid) for validation/batches_by_id.
status	string	Current batch status.
submitted	integer	Total input items submitted.
queued	integer	Prospects queued after freshness and duplicate filtering.
createdProspects	integer	Raw emails inserted into the CRM as new prospects.
skipped	object	Items skipped before validation (`recentlyValidated`, `duplicate`).
estimatedMaxDataTokens	integer	Maximum Data Tokens this batch may spend; actual spend can be lower.
dataTokenBalance	integer	Data Token balance after the batch was queued.

Errors: 400, 401, 403, 406, 409, 415, 422, 429, 500 — shared schema: schemas/errors.

Invoke

Call create with name: "validation/post_emails".