Single email verification
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 synchronous request: https://api-waterfall.bounceban.com/v1/verify/single
Pricing:
- Standard: 1 credit per request.
- Note: Credits are deducted for every request, even if the same email is verified multiple times.
- Custom: Custom rates apply for users on custom plans.
Request
- Base URL: https://api.bounceban.com
- URL: https://api.bounceban.com/v1/verify/single
- Auth: API key in header Authorization
Query parameters
The email that needs to get verified.
(Optional) Setting the verification mode for the verification job. Default mode is regular.<br>
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.<br>
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 accept-all emails. However, it is crucial to obtain the domain for the email owner's current company website from a reliable source, such as the email owner's LinkedIn profile or another trustworthy sales prospecting database. Learn more: https://support.bounceban.com/article/what-is-deepverify
(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 number of events due to inherent limitations. We suggest exploring alternative testing services like TypedWebhook Tools https://typedwebhook.tools/ for a more robust solution. Please note that we are not affiliated with this service.
The webhook event will also include the event-type: single.email_verification_finished header so you can differentiate between different events.<br><br> Please note that the webhook event payload will be in JSON format.
{
"id": "502abcde",
"status": "success",
"email": "dev@bounceban.com",
"result": "deliverable",
"score": 99,
"is_disposable": false,
"is_accept_all": false,
"is_role": true,
"is_free": false,
"mx_records": [
"alt1.aspmx.l.google.com",
"alt2.aspmx.l.google.com",
"alt3.aspmx.l.google.com",
"alt4.aspmx.l.google.com",
"aspmx.l.google.com"
],
"smtp_provider": "Google",
"verify_at": "2022-11-16T07:21:24.943Z",
"credits_consumed": 1.000,
"credits_remaining": 375214.000
}
(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.
Response
ok
Changes
No recorded changes to this operation across all 1 revision of this API.