This release is a pre-release and may not be stable for production use.
Valydar Python SDK
Python client library for the Valydar Identity Verification API.
Installation
pip install valydar
Or from source:
pip install ./sdk/python
Quick Start
from valydar import ValydarClient
client = ValydarClient(api_key="your-api-key")
# Check health
health = client.health()
print(health.status)
# Create a verification
verification = client.create_verification(
client_reference="user-123",
checks=["document", "face_match", "liveness"],
)
print(f"Verification: {verification.id}")
# Upload a document
doc = client.upload_document(
verification.id,
"/path/to/passport.jpg",
document_type="passport",
)
print(f"Document: {doc.document_id}")
# Upload a selfie
selfie = client.upload_selfie(verification.id, "/path/to/selfie.jpg")
# Run face match
result = client.face_match(
verification.id,
doc.document_id,
selfie["document_id"],
)
print(f"Face match: {result.passed}, confidence: {result.confidence}")
API
ValydarClient
| Method | Description |
|---|---|
health() |
Check API health |
list_verifications() |
List all verifications |
create_verification(client_ref, checks) |
Create a new verification |
get_verification(id) |
Get verification status |
upload_document(ver_id, image_path, doc_type) |
Upload a document image |
upload_selfie(ver_id, image_path) |
Upload a selfie |
face_match(ver_id, doc_id, selfie_id) |
Run face comparison |
document_liveness(ver_id, doc_id) |
Check document liveness |
selfie_liveness(ver_id) |
Run passive selfie liveness |
deepfake(ver_id) |
Detect deepfake / AI-generated selfie |
verify_nfc(ver_id, expected_dg1) |
Verify ePassport NFC chip |
active_liveness_challenge(ver_id, type) |
Generate active liveness challenge |
active_liveness_verify(ver_id, challenge_id, frames) |
Verify active liveness |
demo_verify(document_path, selfie_path, checks) |
Run the public no-auth demo |
Release files for valydar 0.1.0a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| valydar-0.1.0a1.tar.gz | 6.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| valydar-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.6 kB
Release files / valydar-0.1.0a1.tar.gz
| Download URL | valydar-0.1.0a1.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
14c051ce805f4137e242fe7883e05bc6c08e01e1c1668d51b9586bc55f9128ca
|
|
BLAKE2b-256 checksum How to use checksums |
87dc6a5a53ffb84edbb6347501a98b6cb00c257395271350cd99a09e479333b8
|
| 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 27, 2026.
Transparency logRelease files / valydar-0.1.0a1-py3-none-any.whl
| Download URL | valydar-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
85618e19a9eedc70a48f01b3daaa572111067069e060ad968ed1321a6a84eb5d
|
|
BLAKE2b-256 checksum How to use checksums |
6a1c946c43fe93b7aa036dd3e3b0a5900735a31d09688fe068b0f9e5b28f66cc
|
| 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 27, 2026.
Transparency log