ZeroBounce

Delete a bulk domain search file and its results from ZeroBounce. DESTRUCTIVE AND IRREVERSIBLE: the results are gone and cannot be downloaded afterwards. ZeroBounce serves this over GET rather than DELETE; it destroys data regardless of the verb.

Report the progress of a bulk domain search job -- the batch form of discovering the email format a domain uses. Its own job family, with its own file ids.

Delete a bulk email finder file and its results from ZeroBounce. DESTRUCTIVE AND IRREVERSIBLE: the found addresses are gone and cannot be downloaded afterwards. ZeroBounce serves this over GET rather than DELETE; it destroys data regardless of the verb.

Report the progress of a bulk email finder job -- the batch form of finding addresses from names and domains. A finder job is its own job family; its file ids are not interchangeable with validation or scoring ids.

List the files available in the account's Amazon S3 input bucket, which is the source the S3 validation and scoring jobs draw from. START HERE for the S3 workflow: this is how a caller learns the exact file_name the job tools need. Both arguments are optional -- with neither, ZeroBounce lists the bucket configured in the account's UI settings.

Report whether an email address has shown recent engagement activity across ZeroBounce's network, and how recently. Answers the 'is this subscriber still alive' question that deliverability alone does not. Spends credits.

Delete a bulk email validation file and its results from ZeroBounce. DESTRUCTIVE AND IRREVERSIBLE: the results are gone and cannot be downloaded afterwards, so retrieve anything needed from the job before calling this. ZeroBounce serves this over GET rather than DELETE; it destroys data regardless of the verb.

Report the progress of a bulk email validation job: whether it is queued, running or complete, how many rows have been processed, and the upload and completion timestamps. Poll this rather than assuming a job is done. Note that this integration cannot CREATE a validation job from an uploaded file -- see the S3 tools, or start the job in the ZeroBounce app.

Report how many API calls the account made over a date range, broken down by validation result (valid, invalid, catch-all, unknown, spamtrap, abuse, do_not_mail) and by the reason codes within them. Both dates are optional; ZeroBounce applies its own window when they are omitted. Costs no credits.

Return the number of validation credits remaining on the connected ZeroBounce account. Takes no arguments. ZeroBounce answers -1 when the credit balance cannot be determined for the key, which is not the same as zero credits. Costs no credits, so this is also the cheapest way to check that a connection still works.

Find a person's email address at a domain, or -- with the domain alone -- the format that domain uses for its addresses (first.last, flast, and so on). Supply as much of the name as is known: with no name ZeroBounce answers the format only, and with a name it also returns the specific address it inferred and the confidence it has in it. Spends credits.

Return ZeroBounce's A.I. quality score for one email address: a 0-10 rating of how likely the address is to be active and engaged, which is a different question from whether it is deliverable. Use alongside validation rather than instead of it -- a valid address can score low. Spends credits.

Delete an A.I. scoring file and its results from ZeroBounce. DESTRUCTIVE AND IRREVERSIBLE: the scores are gone and cannot be downloaded afterwards. ZeroBounce serves this over GET rather than DELETE; it destroys data regardless of the verb.

Report the progress of an A.I. scoring job: whether it is queued, running or complete, and how much of the file has been processed. A scoring job is a separate job family from validation and its file ids are not interchangeable with them.

Validate one email address in real time. Returns the address's status (valid, invalid, catch-all, unknown, spamtrap, abuse or do_not_mail) and a sub_status naming the specific reason, plus whatever ZeroBounce knows about the mailbox: free-mail and role-address flags, the account and domain parts, a suggested correction for an apparent typo, SMTP provider, MX record and, when the optional inputs ask for it, the sender's geolocation, the domain's WHOIS and the address's activity data. SPENDS ONE CREDIT per call (more with verify_plus), so a free account's monthly allowance is finite. Eight options beyond the address itself, all optional -- see each one.

Export a finished validation or scoring file to the account's Amazon S3 export bucket, where the customer's own tooling can read it. THIS IS HOW RESULTS LEAVE ZeroBounce through this integration: the direct result-download endpoints are withheld because they return the whole result file as the response body, which is unbounded. Omit export_bucket to use the bucket configured in the account's UI settings.

Start an A.I. scoring job over a file that is ALREADY in the account's Amazon S3 bucket. Returns the file_id to poll with the scoring filestatus tool -- a scoring id, not interchangeable with a validation one. Get the exact file_name from the S3 file listing first. Spends credits per address.

Add or modify a rule on the account's custom allow/block list, which overrides ZeroBounce's own verdict for the addresses it matches. An allow rule forces a match to validate as valid; a block rule forces it to invalid. Modifies an existing rule rather than duplicating it when the same target and value are already listed, so this is an upsert. Changes how every FUTURE validation on this account answers, not just the caller's own.

Remove a rule from the account's custom allow/block list. DESTRUCTIVE and account-wide: the rule is gone for every future validation on this account, and ZeroBounce offers no undo and no way to list what was removed. Deleting a rule silently changes how addresses that were being forced to valid or invalid are answered from then on.

Validate many email addresses in one real-time call and get back the same per-address result the single validator returns, one entry per address, plus an errors array for the entries ZeroBounce could not process. This is the REAL-TIME batch endpoint: it answers in the same request rather than creating a job, so it needs no file and no polling. SPENDS ONE CREDIT PER ADDRESS, so a large batch can exhaust a free allowance in a single call. For lists larger than a real-time call can carry, use the S3 job tools instead -- this integration does not offer file upload.

Start a bulk email validation job over a file that is ALREADY in the account's Amazon S3 bucket -- the file is named, not uploaded, which is why this tool exists while file upload does not. Returns the file_id to poll with the validation filestatus tool. Get the exact file_name from the S3 file listing first. SPENDS ONE CREDIT PER ADDRESS in the file, so a large list can exhaust an allowance in one job. Note remove_duplicates defaults to TRUE at ZeroBounce.