verifly-email (Python)
Official Python SDK for the Verifly email-verification API.
Package naming. Install
verifly-emailand importverifly_email. The plain nameveriflyon PyPI belongs to an unrelated 2FA company — it is not this project. Always useverifly-email.
- Zero dependencies (pure Python standard library).
- Fully typed, with docstrings on every method.
- Built-in retry with backoff on
429/5xx(honorsRetry-After). - Automatic
Idempotency-Keyforbuy_creditsandsubmit_bulk. - Typed
VeriflyError(code, message, request_id)on API error envelopes.
Install
pip install verifly-email # once published
# or, from this repo:
pip install /path/to/sdks/python
Quick start
from verifly_email import VeriflyClient, VeriflyError
client = VeriflyClient("vf_your_api_key") # base_url defaults to https://verifly.email
try:
r = client.verify("bill.gates@microsoft.com")
print(r["result"]) # deliverable | undeliverable | risky | unknown
print(r["recommendation"]) # safe_to_send | risky | do_not_send
print(r["credits"]) # {"used": 1, "remaining": 99}
except VeriflyError as e:
print(e.code, e.message, e.request_id)
Authentication
Every call (except register) authenticates with your vf_ key, sent as
Authorization: Bearer <api_key>.
client = VeriflyClient(api_key="vf_...", base_url="https://verifly.email")
Create an account programmatically
res = VeriflyClient.register("you@example.com", "a-strong-password")
api_key = res["api_key"]["key"] # shown ONCE — store it now
client = VeriflyClient(api_key)
Methods
| Method | Description |
|---|---|
verify(email) |
Verify a single address. |
verify_batch(emails, deduplicate=True, ...) |
Verify up to 100 addresses synchronously. |
clean(emails, options=None) |
Clean/filter a list (no verification, no credits). |
extract(text, deduplicate=True, lowercase=True) |
Pull email addresses out of text/CSV. |
submit_bulk(emails=None, text=None, webhook_url=None, ...) |
Create an async bulk job (up to 1M). |
jobs(status=None, limit=None, offset=None) |
List bulk jobs. |
job(job_id) |
Get a bulk job's status. |
job_results(job_id) |
Get a completed job's per-email results. |
account() |
Account profile + credit summary. |
credits() |
Current credit balance. |
usage(period=None, limit=None) |
API usage summary (day/week/month). |
packages() |
List credit packages and prices. |
payment_history() |
List payment history. |
buy_credits(package_id, method="stripe", currency=None) |
Create a Stripe/crypto checkout. |
VeriflyClient.register(email, password) (classmethod) |
Self-register, returns account + API key. |
Examples
# Batch (<=100), synchronous
batch = client.verify_batch(
["a@example.com", "b@example.com"],
exclude_role_accounts=True,
)
for item in batch["results"]:
print(item["email"], item["result"])
# List hygiene without spending credits
print(client.clean(["A@Example.com ", "a@example.com", "bad"])["..."])
print(client.extract("contact us at sales@acme.io or ceo@acme.io"))
# Async bulk + polling
job = client.submit_bulk(emails=[...], webhook_url="https://you/webhook")
status = client.job(job["job_id"] if "job_id" in job else job["job"]["id"])
results = client.job_results(job_id)
# Account / billing
print(client.credits())
print(client.packages())
checkout = client.buy_credits("pro", method="stripe")
checkout = client.buy_credits("pro", method="crypto", currency="USDT")
Errors
API error envelopes ({"success": false, "error": {...}}) and non-2xx
responses raise VeriflyError:
try:
client.verify("nope")
except VeriflyError as e:
e.code # e.g. "invalid_email", "insufficient_credits", "rate_limit_exceeded"
e.message
e.request_id # from the x-request-id response header
e.status # HTTP status
e.suggestion # optional remediation hint
Retries & idempotency
429and5xxresponses are retried (default 3 times) with exponential backoff, honoring theRetry-Afterheader. Configure viaVeriflyClient(..., max_retries=N, timeout=seconds).buy_creditsandsubmit_bulksend anIdempotency-Keyheader. One is auto-generated per call; pass your own withidempotency_key=...to make a specific retry safe end-to-end.
License
MIT
Metadata
Release files for verifly-email 1.0.0
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 | Actions |
|---|---|---|---|---|
| verifly_email-1.0.0.tar.gz | 9.8 kB | Without provenance | Details for verifly_email-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| verifly_email-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for verifly_email-1.0.0-py3-none-any.whl |
Total release size: 18.7 kB
Release files / verifly_email-1.0.0.tar.gz
| Download URL | verifly_email-1.0.0.tar.gz |
|---|---|
| Size | 9.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
21e4afc3ceedd58bca5075700d5937771987a154a680b2d601d5e179fbde9074
|
|
BLAKE2b-256 checksum How to use checksums |
1a41f4e5fe494d0bab0582a6ddd08068a2f39d205cb855d9c66c3456cf8100f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / verifly_email-1.0.0-py3-none-any.whl
| Download URL | verifly_email-1.0.0-py3-none-any.whl |
|---|---|
| Size | 9.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ecf522ad8725c34752336e7a563f19d43c97a349b2bfba0d1694ccb2fd2f12bd
|
|
BLAKE2b-256 checksum How to use checksums |
238cb847c6be0958d790dc5f0e5d42d0503e23f462ff042c778feeeaa6a52106
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for verifly-email 1.0.0
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.