BounceBan: Get Bulk Emails

Get the verification results for specific email addresses within a bulk verification task.

Tool ID: bounceban_get_bulk_emails

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'bounceban_get_bulk_emails',
  {
    "id": "id_123",
    "emails": [
      "jane.doe@example.com"
    ]
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute bounceban_get_bulk_emails --input '{
  "id": "id_123",
  "emails": [
    "jane.doe@example.com"
  ]
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "result": "ok",
    "status": "importing",
    "items": [
      {
        "status": "success",
        "email": "jane.doe@example.com",
        "result": "deliverable"
      }
    ]
  }
}

Use deepline describe bounceban_get_bulk_emails --json for the latest machine-readable contract.

Input reference

To retrieve verification results for specific emails from your bulk verification task, provide the task ID along with the chosen email addresses.

Name	Type	Required	Default	Details
`payload.id`	`string`	Yes	—	(Required) Bulk email verification task ID.
`payload.emails`	`array`	Yes	—	Specify the list of emails to retrieve verification results, with a maximum limit of 100 emails. Include only emails from the bulk verification task associated with the given task ID. Maximum items: 100.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.result`	`"ok" \| "err"`	No	—	> `ok` Indicates the request is successful. > `err` The bulk task has not finished yet, please try again later. Allowed: `ok`, `err`.
`result.data.status`	`"importing" \| "verifying" \| "finished"`	No	—	Bulk email verification task status. > `importing` indicates the list of emails are being imported for verification. > `verifying` indicates all the emails are imported and are being verified. > `finished` indicates verification for the whole list has finished. Allowed: `importing`, `verifying`, `finished`.
`result.data.items`	`array`	No	—	Detailed verification results for each email.
`result.data.items[].status`	`"success" \| "verifying" \| "queue"`	No	—	Verification status for this task. > `success` indicates the task is finished and the final verification result can be returned. > `verifying` indicates the email is still being verified. > `queue` indicates the email is still being in queue. Allowed: `success`, `verifying`, `queue`.
`result.data.items[].email`	`string`	No	—	The email address submitted for verification.
`result.data.items[].result`	`"deliverable" \| "risky" \| "undeliverable" \| "unknown"`	No	—	The state (verification result) for the email. Allowed: `deliverable`, `risky`, `undeliverable`, `unknown`.
`result.data.items[].score`	`integer`	No	—	The score (0 ~ 100) represents the deliverability of an email - the higher, the better. Minimum: 0. Maximum: 100.
`result.data.items[].is_disposable`	`boolean`	No	—	Whether the email is disposable.
`result.data.items[].is_accept_all`	`boolean`	No	—	Whether the email is accept-all.
`result.data.items[].is_role`	`boolean`	No	—	Whether the email is role based.
`result.data.items[].is_free`	`boolean`	No	—	Whether the email is a free email.
`result.data.items[].mx_records`	`array`	No	—	All MX records for the email.
`result.data.items[].smtp_provider`	`string`	No	—	SMTP provider based on the main MX record, e.g. if the MX record for an email is `alt1.aspmx.l.google.com`, then the smtp provider will be `Google`.
`result.data.items[].mode`	`string`	No	—	Verification mode.
`result.data.items[].verify_at`	`string`	No	—	The time the verification task finished. Format: `date-time`.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation