Bulk jobs

Bulk jobs verify many addresses asynchronously. The flow is: create a job → add addresses → commit → poll progress → export results.

Method	Path	Purpose
POST	/v1/bulk-verifications	Create a job.
POST	/v1/bulk-verifications/{jobId}/items	Add addresses in chunks of up to 500.
POST	/v1/bulk-verifications/{jobId}/commit	Seal the input and start verifying.
GET	/v1/bulk-verifications/{jobId}	Poll progress and the running verdict tally.
GET	/v1/bulk-verifications/{jobId}/items	Page through the results in row_index order.

Costs 1 credit per address

Bulk jobs bill 1 credit per address, the same rate as a real-time verification. Duplicates within a job are verified once and charged once. If you are checking a list rather than gating a live signup form, this is the endpoint built for it.

A job holds up to 100,000 rows. Every request takes Authorization: Bearer sk_your_api_key; a jobId that is not yours returns 404 {"error":"Job not found"}.

The flow

1. Create a job — returns the jobId every later call uses.
2. Add addresses — upload the list in chunks of 1–500 rows, each with its row_index.
3. Commit the job — seals the input and starts verification.
4. Poll progress — until status is completed.
5. Export the results — page through the rows and their result objects.

See also

• Verify a single email — the result object, verdicts, and signals
• Understanding results
• Errors