> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# BounceBan: Get Single Status

> Get the result of a single email verification by id; does not cost verification credits. Includes inputs, outputs, SDK V2 examples, and Deepline cost.

Get the result of a single email verification by id; does not cost verification credits.

<Info>
  Tool ID: `bounceban_get_single_status`
</Info>

## 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.

```ts theme={null}
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

```bash theme={null}
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.

```json theme={null}
{
  "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](#tag/Single-verification/paths/~1v1~1verify~1single/get) 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. |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "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.",
    "properties": {
      "id": {
        "type": "string",
        "description": "The unique id returned by every successful request to the [/v1/verify/single](#tag/Single-verification/paths/~1v1~1verify~1single/get) 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 efficient approach, we highly recommend using a webhook event to listen for verification results. You can set this up by providing a callback URL via the `url` parameter in your [/verify/single](#tag/Single-verification/paths/~1v1~1verify~1single/get) API request, allowing results to be sent to your system without the need for repeated polling."
      }
    },
    "required": [
      "id"
    ],
    "additionalProperties": false
  }
  ```
</details>

## 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](#tag/Single-verification/paths/~1v1~1verify~1single~1status/get) 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](#tag/Single-verification/paths/~1v1~1verify~1single~1status/get) 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](#tag/Single-verification/paths/~1v1~1verify~1single~1status/get) 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). |

<details>
  <summary>Show raw output schema</summary>

  ### Output JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "type": "object",
        "description": "Verification result for this task.",
        "properties": {
          "id": {
            "type": "string",
            "description": "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](#tag/Single-verification/paths/~1v1~1verify~1single~1status/get) endpoint, if you don’t want to receive it through webhook events by setting a target URL with the url parameter. The ID is valid for 90 days, however, exercise caution when relying on verification results after an extended period, for example, 2 weeks."
          },
          "status": {
            "type": "string",
            "description": "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](#tag/Single-verification/paths/~1v1~1verify~1single~1status/get) API with the provided `id`. Alternatively, you can receive the results via a webhook by specifying a target URL with the `url` parameter. Please DO NOT send the same requests repeatedly as each request will cost 1 credit . > `queue` Indicates that the rate limit for your account is reached and the email is queued for verification. In such cases, please poll for the verification results using the [/single/status](#tag/Single-verification/paths/~1v1~1verify~1single~1status/get) API with the provided `id`. Alternatively, you can receive the results via a webhook by specifying a target URL with the `url` parameter. Please DO NOT send the same requests repeatedly as each request will cost 1 credit .",
            "enum": [
              "success",
              "verifying",
              "queue"
            ]
          },
          "try_again_at": {
            "type": "integer",
            "description": "The recommended Unix timestamp to poll the [/single/status](#tag/Single-verification/paths/~1v1~1verify~1single~1status/get) endpoint for an updated verification result. This value is only returned when the verification status is `verifying`."
          },
          "email": {
            "type": "string",
            "description": "The email address submitted for verification."
          },
          "result": {
            "type": "string",
            "description": "The state (verification result) for the email.",
            "enum": [
              "deliverable",
              "risky",
              "undeliverable",
              "unknown"
            ]
          },
          "score": {
            "type": "integer",
            "description": "The score (0 ~ 100) represents the deliverability of an email - the higher, the better.",
            "minimum": 0,
            "maximum": 100
          },
          "is_disposable": {
            "type": "boolean",
            "description": "Whether the email is disposable."
          },
          "is_accept_all": {
            "type": "boolean",
            "description": "Whether the email is accept-all."
          },
          "is_role": {
            "type": "boolean",
            "description": "Whether the email is role based."
          },
          "is_free": {
            "type": "boolean",
            "description": "Whether the email is a free email."
          },
          "mx_records": {
            "type": "array",
            "description": "All MX records for the email.",
            "items": {
              "type": "string"
            }
          },
          "smtp_provider": {
            "type": "string",
            "description": "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."
          },
          "mode": {
            "type": "string",
            "description": "Verification mode."
          },
          "verify_at": {
            "type": "string",
            "description": "The time the verification task finished.",
            "format": "date-time"
          }
        },
        "additionalProperties": false
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Deepline cost

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

## Related documentation

* [BounceBan provider guide](/docs/providers/bounceban/guide)
* [SDK V2 quickstart](/docs/sdk-v2/quickstart)
* [SDK reference](/docs/sdk-v2/sdk-reference)
* [Run tools across a CSV](/docs/sdk-v2/batch-csv)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.