veqen (Python)
Official Python client for Veqen: catch disposable emails, typos, datacenter and Tor IPs, and VoIP numbers with one API call.
pip install https://veqen-app.com/static/sdk/veqen-0.1.0-py3-none-any.whl
from veqen import Veqen, VeqenError
client = Veqen() # reads VEQEN_API_KEY from the environment
result = client.signup(email="jane@mailinator.com", ip="185.220.101.1")
print(result["risk"]["verdict"]) # "refuse"
for reason in result["risk"]["reasons"]:
print(reason["code"], reason["message"])
| Method | Endpoint | Credits |
|---|---|---|
email(address, verify_mailbox=False) |
/v1/email/check |
1 (+5) |
emails(list) |
/v1/email/batch (chunks of 100) |
1 each |
ip(address) |
/v1/ip/check |
1 |
phone(number, country=None) |
/v1/phone/check |
1 |
domain(name) |
/v1/domain/check |
1 |
signup(email=, ip=, phone=, phone_country=) |
/v1/signup/check |
3 |
account(), usage(days=30) |
/v1/account, /v1/usage |
0 |
Errors raise VeqenError with .status, .type (e.g. insufficient_credits) and .message. Requests are retried on 429 and 5xx. Docs: https://veqen-app.com/docs
1 maintainer
Metadata
1 maintainer
Release files for veqen 0.1.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 | |
|---|---|---|---|---|
| veqen-0.1.0.tar.gz | 5.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| veqen-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.0 kB
Release files / veqen-0.1.0.tar.gz
| Download URL | veqen-0.1.0.tar.gz |
|---|---|
| Size | 5.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b25a89b0ad8943eb21dce102745d61c5a0fb262ef0a5cbeb3c5eab4352c1922
|
|
BLAKE2b-256 checksum How to use checksums |
8b2f486dc8c2b15105cfe9de716c7300c2d2953c5c3a39745ae0117643f4e9a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / veqen-0.1.0-py3-none-any.whl
| Download URL | veqen-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
22e6053052b971feb0a4caca57b46d5178a3963d66a25d99cc49861c41af339c
|
|
BLAKE2b-256 checksum How to use checksums |
90e844b22c97f09c45f2db5ce4645bd5f13c3bb98edcb0d7483a6ca5d401b60c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for veqen 0.1.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for veqen-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA 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.
