Overview
The client library for Bulk Email Verification API in Python language.
The minimum Python version is 3.6.
Installation
pip install bulk-email-verifier
Examples
Full API documentation available here
Create a new client
from bulkemailverifier import *
client = Client('Your API key')
Create bulk request
emails = [
'example@example.com',
'test@example.org',
'test'
]
request_id = client.create_request(emails=emails)
Get request status
result = client.get_status(request_ids=[request_id])
# Finished once result.data[i].ready == True
print(result)
Get email records
completed = client.get_records(request_id=request_id)
# Invalid and failed emails
failed = client.get_records(request_id=request_id, return_failed=True)
List your requests
result = client.get_requests()
Download CSV result
client.download(filename='emails.csv', request_id=request_id)
Extras
# Paginate over request IDs in descending order and get results in XML
result = client.get_requests_raw(
only_ids=True,
page=2,
per_page=20,
sort=Client.SORT_DESC,
output_format=Client.XML_FORMAT
)
Response model overview
ResponseRecords:
- data: [Record]
- email_address: str
- format_check: bool
- smtp_check: bool
- dns_check: bool
- free_check: bool
- disposable_check: bool
- catch_all_check: bool
- result: str
- error: str
- mx_records: [str]
ResponseRequests:
- current_page: int
- from_requests: int
- last_page: int
- per_page: int
- to_requests: int
- total: int
- data: [BulkRequest]
- id: int
- date_start: datetime.datetime
- total_emails: int
- invalid_emails: int
- processed_emails: int
- failed_emails: int
- ready: bool
ResponseStatus:
- data: [BulkRequest]
Changelog
1.0.1 (2022-01-18)
First release
Metadata
Release files for bulk-email-verifier 1.0.1
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 |
|---|---|---|---|---|
| bulk-email-verifier-1.0.1.tar.gz | 12.2 kB | Without provenance | Details for bulk-email-verifier-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bulk_email_verifier-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for bulk_email_verifier-1.0.1-py3-none-any.whl |
Total release size: 24.2 kB
Release files / bulk-email-verifier-1.0.1.tar.gz
| Download URL | bulk-email-verifier-1.0.1.tar.gz |
|---|---|
| Size | 12.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6b7e451dbc0aadcc486c342b69ce6e4688c23c3b462554706cfe13d70c5358d3
|
|
BLAKE2b-256 checksum How to use checksums |
9fb63d6714efd7cf3dace01cc9712a27a7b9ecc0def9ce32782fdc28c6326c23
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.3
|
Release files / bulk_email_verifier-1.0.1-py3-none-any.whl
| Download URL | bulk_email_verifier-1.0.1-py3-none-any.whl |
|---|---|
| Size | 12.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3db229ebd5c382aa3fe350c785de7fe34016da87f26ff565040df346c8cfe1fb
|
|
BLAKE2b-256 checksum How to use checksums |
32d133e130d61984f999eb783ad09594d068b57545fb54056c4cff023007052c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.1 pkginfo/1.8.2 requests/2.27.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.3
|
Security for bulk-email-verifier 1.0.1
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.