wavalid-py-sdk
Python SDK for the wavalid WhatsApp number validation API. wavalid checks whether a phone number is registered and active on WhatsApp; it does not send messages and does not store phone numbers.
Install
pip install wavalid-py-sdk
Requires Python 3.9+. No dependencies — uses the standard library urllib.
Authentication
Every request needs an API key, created from the wavalid dashboard. Never hardcode it — read it from an environment variable.
import os
from wavalid import WavalidClient
client = WavalidClient(api_key=os.environ["WAVALID_API_KEY"], base_url="https://wavalid.com")
base_url is the root domain only — do not append /api or /api/v1, the client adds that path itself.
client.validate(phone_number, batch_id=None)
Validates a single phone number.
result = client.validate("+14155551234")
# result["status"]: "valid" | "invalid" | "limit"
client.validate_bulk(phone_numbers, batch_id=None)
Validates up to 100 phone numbers in one request.
bulk = client.validate_bulk(["+14155551234", "+447911123456"])
# bulk["results"], bulk["creditsUsed"], bulk["creditsRemaining"]
For more than 100 numbers, split the list into chunks of 100 and call validate_bulk once per chunk.
Errors
Both methods raise wavalid.ApiError on any non-2xx response — always wrap calls in try/except, never assume success.
from wavalid import ApiError
try:
result = client.validate("+14155551234")
except ApiError as error:
if error.code == "rateLimitExceeded":
... # back off and retry later
print(error.status_code, error.code, error.message)
| status_code | code | meaning |
|---|---|---|
| 400 | (none) | phone_number is not a valid international number, or phone_numbers is empty/over 100 |
| 401 | (none) | missing or invalid API key |
| 402 | insufficientCredits |
account has no credits left |
| 404 | (none) | batch_id does not exist for this account |
| 429 | rateLimitExceeded |
too many requests; back off |
| 502 | (none) | upstream WhatsApp check failed; safe to retry |
Links
- API reference: https://wavalid.com/product/api
- Source / issues: https://github.com/rizonllc/wavalid-py-sdk
- License: MIT
Release files for wavalid-py-sdk 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 | |
|---|---|---|---|
| wavalid_py_sdk-0.1.0.tar.gz | 2.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wavalid_py_sdk-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.4 kB
Release files / wavalid_py_sdk-0.1.0.tar.gz
| Download URL | wavalid_py_sdk-0.1.0.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b461227dd918bce554989902fbfa49ad796a3a20099a215daeec1834db09bc6
|
|
BLAKE2b-256 checksum How to use checksums |
30d6fef821917ddd79498c26772652fae3bb8c4fd97b2afdd40e12b3586f4f20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 1, 2026.
Transparency logRelease files / wavalid_py_sdk-0.1.0-py3-none-any.whl
| Download URL | wavalid_py_sdk-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a7c8680044d055e09f34569eedf68406cb4400d256a8af201a8ae824adf3576e
|
|
BLAKE2b-256 checksum How to use checksums |
cbd57efe64a65bf4172f82a94a6f551ae2ebee5d370be5a99abac04bc1c6a3e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 1, 2026.
Transparency log