BounceBan: Get Single Status

Inspect BounceBan account credits and rate limits.

Tool ID: bounceban_get_single_status

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_get_single_status',
  {
    "id": "id_123"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute bounceban_get_single_status --input '{
  "id": "id_123"
}' --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_get_single_status --json for the latest machine-readable contract.

Input reference

Get the verification result for single email verification. Requests to this endpoint don’t cost verification credits. The result will be available for 90 days after verification.

Name	Type	Required	Default	Details
`payload.id`	`string`	Yes	—	The unique id returned by every successful request to the /v1/verify/single endpoint. > Please consider implementing rate limiting for polling requests to avoid excessive traffic. We recommend capping polling to no more than 10 requests for the same verification `id` within a 5-minute period. After 5 minutes, polling should stop if no results are available, and a new verification request should be initiated instead. > For a more See the live schema for the complete constraint.

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: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

Get started

Build and automate

Common workflows

Data and integrations

Reference

BounceBan: Get Single Status

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