Vonage Legacy Verify Package
This package contains the code to use Vonage's legacy Verify API in Python. This package includes methods for working with 2-factor authentication (2FA) messages sent via SMS or TTS.
Note: There is a more current package available: Vonage's Verify API, which is recommended for most use cases. The newer API lets you send messages via multiple channels, including Email, SMS, MMS, WhatsApp, Messenger and others. You can also make Silent Authentication requests with the new Verify package to give an end user a more seamless experience.
Usage
It is recommended to use this as part of the main vonage package. The examples below assume you've created an instance of the vonage.Vonage class called vonage_client.
Make a Verify Request
from vonage_verify_legacy import VerifyRequest
params = {'number': '1234567890', 'brand': 'Acme Inc.'}
request = VerifyRequest(**params)
response = vonage_client.verify_legacy.start_verification(request)
Make a PSD2 (Payment Services Directive v2) Request
from vonage_verify_legacy import Psd2Request
params = {'number': '1234567890', 'payee': 'Acme Inc.', 'amount': 99.99}
request = VerifyRequest(**params)
response = vonage_client.verify_legacy.start_verification(request)
Check a Verification Code
vonage_client.verify_legacy.check_code(request_id='my_request_id', code='1234')
Search Verification Requests
# Search for single request
response = vonage_client.verify_legacy.search('my_request_id')
# Search for multiple requests
response = vonage_client.verify_legacy.search(['my_request_id_1', 'my_request_id_2'])
Cancel a Verification
response = vonage_client.verify_legacy.cancel_verification('my_request_id')
Trigger the Next Workflow Event
response = vonage_client.verify_legacy.trigger_next_event('my_request_id')
Request a Network Unblock
Note: Network Unblock is switched off by default. Contact Sales to enable the Network Unblock API for your account.
response = vonage_client.verify_legacy.request_network_unblock('23410')
Metadata
Release files for vonage-verify-legacy 1.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 | Actions |
|---|---|---|---|---|
| vonage_verify_legacy-1.1.0.tar.gz | 8.5 kB | Without provenance | Details for vonage_verify_legacy-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vonage_verify_legacy-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for vonage_verify_legacy-1.1.0-py3-none-any.whl |
Total release size: 17.3 kB
Release files / vonage_verify_legacy-1.1.0.tar.gz
| Download URL | vonage_verify_legacy-1.1.0.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e08fbf57a8264c65a6e8024067e238f3363f97e80b18776d7930c9d5d97c7406
|
|
BLAKE2b-256 checksum How to use checksums |
a57ec81e61ceb7b58b63af0a31f2ca035470d1ee3019a4df3dcd13f7e50aaedb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.3
|
Release files / vonage_verify_legacy-1.1.0-py3-none-any.whl
| Download URL | vonage_verify_legacy-1.1.0-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
51689afc5cadf6dcc8239a16fe617e5b57c55a6700529d1cbee870cf8ce76c45
|
|
BLAKE2b-256 checksum How to use checksums |
dd0bd8667dcbb9877434c95dd289590f8d2aa224492cd78d75669becc29a07eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.3
|
Security for vonage-verify-legacy 1.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.
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.