byebouncer-sdk
Official Python SDK for the ByeBouncer email verification API.
Sync and async clients, real-time single-email verification, bulk CSV verification (up to 50k emails per job), HMAC-signed webhooks.
Install
pip install byebouncer-sdk
Requires Python 3.9+.
The distribution is named byebouncer-sdk; the Python import remains byebouncer.
To upgrade an existing installation, run pip install --upgrade byebouncer-sdk.
The default API URL is https://api.byebouncer.com; each user supplies their own
secret API key from the dashboard. Keep keys in environment variables on your server.
Quickstart
import os
from byebouncer import ByeBouncer
with ByeBouncer(api_key=os.environ["BB_API_KEY"]) as client:
result = client.verify("user@gmail.com")
print(result.status) # "deliverable" | "undeliverable" | "risky" | "unknown"
print(result.action) # "allow" | "review" | "block"
print(result.signals) # ["valid_syntax", "mx_found", ...]
print(result.credits_remaining)
Get your BB_API_KEY from https://byebouncer.com/dashboard (format bb_live_...).
Async
import asyncio
from byebouncer import AsyncByeBouncer
async def main():
async with AsyncByeBouncer(api_key="bb_live_...") as client:
result = await client.verify("user@gmail.com")
print(result.status)
asyncio.run(main())
Bulk verification
created = client.bulk(
emails=["a@gmail.com", "b@outlook.com"], # up to 5.000
filename="my_list.csv",
webhook_url="https://api.myapp.com/hooks/byebouncer", # optional
)
job = created.job
print(f"Job {job.id}, {job.total_emails} emails")
print(f"Estimated duration: {created.estimated_seconds}s")
# Present when webhook_url is supplied (generated or supplied).
# Store it now: it is never returned by later job reads.
webhook_secret = created.webhook_secret
Polling for completion
import httpx
final = client.bulk_wait_for_completion(
job.id,
interval_seconds=3,
on_progress=lambda j: print(f"{j.processed}/{j.total_emails}"),
)
if final.status == "completed":
download = client.bulk_download_url(final.id)
response = httpx.get(download.url, timeout=30)
response.raise_for_status()
csv = response.text
open("results.csv", "w").write(csv)
Webhooks (recommended for large jobs)
Prefer webhooks over polling. On completion ByeBouncer POSTs to your URL with:
X-ByeBouncer-Event: bulk.completed
X-ByeBouncer-Signature: <hex HMAC-SHA256(body, webhook_secret)>
Attach or rotate the webhook after creating the job:
result = client.bulk_set_webhook(
job.id,
webhook_url="https://api.myapp.com/hooks/byebouncer",
)
webhook_secret = result.webhook_secret # store it NOW, returned only once
Cancel
cancelled = client.bulk_cancel(job.id)
print(f"Refunded {cancelled.credits_refunded} credits")
Error handling
Non-2xx responses raise ByeBouncerError or a subclass with code, status, detail.
from byebouncer import InsufficientCreditsError, RateLimitError, ByeBouncer
with ByeBouncer(api_key="bb_live_...") as client:
try:
client.verify("user@gmail.com")
except InsufficientCreditsError as e:
print(f"Out of credits (remaining: {e.credits_remaining})")
except RateLimitError as e:
print(f"Rate limited, retry after {e.retry_after_seconds}s")
API reference
Every method mirrors the OpenAPI spec.
| Method | Endpoint | Description |
|---|---|---|
verify(email) |
POST /verify |
Verify a single email |
credits() |
GET /credits |
Get balance |
bulk(emails, ...) |
POST /bulk |
Enqueue a bulk job |
bulk_status(job_id) |
GET /bulk/{id} |
Fetch job |
bulk_cancel(job_id) |
DELETE /bulk/{id} |
Cancel |
bulk_download_url(job_id) |
GET /bulk/{id}/download |
Signed CSV URL |
bulk_set_webhook(job_id, ...) |
POST /bulk/{id}/webhook |
Attach/rotate webhook |
bulk_wait_for_completion(job_id, ...) |
polls | Convenience helper |
bulk_and_wait(emails, ...) |
create+poll+download | Available in sync and async clients |
Production use
Clients use a 30-second network timeout by default, including CSV downloads.
Configure timeout= for slower connections. When supplying your own httpx
client, configure its timeout directly and close it yourself.
Bulk helpers raise bulk_not_completed for failed, cancelled or expired jobs
and for completed jobs without downloadable results. Prefer webhooks for large jobs.
Requests are not automatically retried: a timed-out verification may already have
consumed credits. To retry bulk creation safely, reuse the same idempotency_key
with bulk().
Support
- Docs: https://byebouncer.com/docs
- Email: hello@byebouncer.com
- Issues: https://github.com/fidelp27/byebouncer/issues
License
MIT © ByeBouncer
Metadata
Release files for byebouncer-sdk 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| byebouncer_sdk-0.2.2.tar.gz | 13.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| byebouncer_sdk-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.2 kB
Release files / byebouncer_sdk-0.2.2.tar.gz
| Download URL | byebouncer_sdk-0.2.2.tar.gz |
|---|---|
| Size | 13.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b39d6dd439e529c88855d71583ce7cbf938ad6038a9b59d2713f7e15b103579
|
|
BLAKE2b-256 checksum How to use checksums |
deaee0835f3c5f42fb4c40a829325fd509b7c8231331831a2743f2784021b689
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.5
|
Release files / byebouncer_sdk-0.2.2-py3-none-any.whl
| Download URL | byebouncer_sdk-0.2.2-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8e4a852a1b25f69b2500c5d343b95f974d19bd394ae5ee4562363d59a9f72694
|
|
BLAKE2b-256 checksum How to use checksums |
934511d441fa70feaa3a6f73c7f654b0f84ea4798ea950fe04dca686106af35d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.5
|
Security for byebouncer-sdk 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.