BounceBan: Verify Single

Verify one email address before sending.

Tool ID: bounceban_verify_single

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'bounceban_verify_single',
  {
    "email": "jane.doe@example.com"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute bounceban_verify_single --input '{
  "email": "jane.doe@example.com"
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "id": "id_123",
    "status": "success",
    "try_again_at": 123
  }
}

Use deepline tools get bounceban_verify_single --json for the latest machine-readable contract.

Input reference

Overview: This endpoint is designed for advanced users requiring granular control over BounceBan server connections. Timeout & Async Handling: This request has a 15-second timeout. If verification completes within this window, the result is returned immediately. If verification exceeds 15 seconds, the API returns a 200 OK response containing a transaction id and the status verifying. You can retrieve the final result in two ways: * Polling: Use the returned id to query the v1/verify/single/status endpoint. * Webhook: specific a url parameter in your initial request to receive the result via webhook. Alternative for Long Connections: If your infrastructure supports long-held GET connections (e.g., Clay, n8n), we recommend using the Waterfall API instead to receive results in a single See the live schema below for the complete notes.

Name	Type	Required	Default	Details
`payload.email`	`string`	Yes	—	The email that needs to get verified.
`payload.mode`	`"regular" \| "deepverify"`	No	—	(Optional) Setting the verification mode for the verification job. Default mode is `regular`. > `regular`: The default option for email verification. It does not assume that the domain of the email owner’s current company website matches the domain of the email being verified. > `deepverify`: DeepVerify operates on the assumption that the domain of the email owner’s current company website matches the domain of the email being verified. This assumption can improve the success rate of verifying See the live schema for the complete constraint.
`payload.url`	`string`	No	—	(Optional) A webhook target URL specified to receive verification result event in real-time through an HTTP POST request. In case of a failed webhook event delivery, the system will attempt to resend the event up to two additional times within a short interval. For those verifying a substantial volume of emails, it’s crucial to ensure that your webhook server is equipped to manage the incoming traffic. Services such as ngrok have been known to encounter issues when dealing with a significant See the live schema for the complete constraint.
`payload.disable_catchall_verify`	`"0" \| "1"`	No	—	(Optional) Defaults to `0`. When set to `1`, BounceBan performs only basic SMTP verification. This may leave catch-all emails or those protected by ESGs (Email Security Gateways) unverified. For these addresses, the API will return `result: 'unknown'`, `score: -1`, and the credit cost is 0. Allowed: `0`, `1`.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Verification result for this task.
`result.data.id`	`string`	No	—	Unique ID for this single verification task. This parameter is returned for all status values. If verification result is not available for a request in 15 seconds, the response for this endpoint will not include other verification information (e.g. score, deliverable or not deliverable, etc.) and you should use this ID to poll for the verification result via the /single/status endpoint, if you don’t want to receive it through See the live schema for the complete constraint.
`result.data.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 that the email is still undergoing verification. A small percentage of emails, particularly those using greylisting technologies, may not return verification results in real time. In such cases, please poll for the verification results using the /single/status API with the See the live schema for the complete constraint.
`result.data.try_again_at`	`integer`	No	—	The recommended Unix timestamp to poll the /single/status endpoint for an updated verification result. This value is only returned when the verification status is `verifying`.
`result.data.email`	`string`	No	—	The email address submitted for verification.
`result.data.result`	`"deliverable" \| "risky" \| "undeliverable" \| "unknown"`	No	—	The state (verification result) for the email. Allowed: `deliverable`, `risky`, `undeliverable`, `unknown`.
`result.data.score`	`integer`	No	—	The score (0 ~ 100) represents the deliverability of an email - the higher, the better. Minimum: 0. Maximum: 100.
`result.data.is_disposable`	`boolean`	No	—	Whether the email is disposable.
`result.data.is_accept_all`	`boolean`	No	—	Whether the email is accept-all.
`result.data.is_role`	`boolean`	No	—	Whether the email is role based.
`result.data.is_free`	`boolean`	No	—	Whether the email is a free email.
`result.data.mx_records`	`array`	No	—	All MX records for the email.
`result.data.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`. Currently a value is only returned if the MX records are notable.
`result.data.mode`	`string`	No	—	Verification mode.
`result.data.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: per_result (per result).
Estimated Deepline credits: 0.06 per pricing unit.

Get started

Build and automate

Common workflows

Data and integrations

Reference

BounceBan: Verify Single

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​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