Registry / communication / telesignenterprise

telesignenterprise

JSON →
library4.1.0pypypi✓ verified 22d ago

The TeleSign Enterprise SDK for Python simplifies integration with TeleSign's APIs for phone verification, SMS messaging, and fraud prevention services. It allows developers to quickly add security and communication features to their applications. The current version is 4.0.1, and the library maintains an active development status with updates primarily released to support new TeleSign API features, address critical bugs, or incorporate breaking changes from their backend services.

pip install telesignenterprise
INSTALL
IMPORT
SIG · TELESIGNENTERPRISE
T
telesignenterprise
communicationpythonv4.1.0
Install
2.3s avg
Import
354ms
Disk
19MB
Pass rate
10/ 10
Env Coverage10 / 10
glibc
3.93.13
musl
3.93.13
Install & Compatibility
Where this runs
tested against v4.1.0 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
py 3.103.95 runs
installs and imports cleanly · install 0.0s · import 0.360s · 21.3MB
glibc
py 3.103.95 runs
installs and imports cleanly · install 2.3s · import 0.348s · 22MB
19MB installed
● package 19MB
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

RestClient
from telesign.rest import RestClient
from telesignenterprise.rest import RestClient
The top-level package is `telesign`, not `telesignenterprise`, even though the PyPI package is named `telesignenterprise`.
TeleSignUtils
from telesign.util import TeleSignUtils
Utility functions are available under `telesign.util`.

This quickstart demonstrates how to initialize the `RestClient` with your TeleSign Customer ID and API Key (preferably from environment variables) and then use it to send an SMS message and perform a PhoneID lookup. Ensure you replace the placeholder values or set corresponding environment variables.

import os from telesign.rest import RestClient CUSTOMER_ID = os.environ.get('TELE_CUSTOMER_ID', 'YOUR_CUSTOMER_ID') API_KEY = os.environ.get('TELE_API_KEY', 'YOUR_API_KEY') PHONE_NUMBER = os.environ.get('TELE_PHONE_NUMBER', '+1234567890') # E.164 format if __name__ == '__main__': if CUSTOMER_ID == 'YOUR_CUSTOMER_ID' or API_KEY == 'YOUR_API_KEY' or PHONE_NUMBER == '+1234567890': print("Please set TELE_CUSTOMER_ID, TELE_API_KEY, and TELE_PHONE_NUMBER environment variables or replace placeholders.") else: try: telesign_client = RestClient(CUSTOMER_ID, API_KEY) # Example: Send an SMS message response = telesign_client.sms.message(PHONE_NUMBER, "Hello from TeleSign!", message_type="ARN") if response.status_code == 200: print(f"SMS message sent successfully: {response.json()}") else: print(f"Failed to send SMS message: {response.status_code} - {response.json()}") # Example: Check PhoneID (basic) phoneid_response = telesign_client.phoneid.standard(PHONE_NUMBER, {}) # Second arg is optional 'ucid' if phoneid_response.status_code == 200: print(f"PhoneID Standard lookup successful: {phoneid_response.json()}") else: print(f"Failed PhoneID Standard lookup: {phoneid_response.status_code} - {phoneid_response.json()}") except Exception as e: print(f"An error occurred: {e}")
Debug
Known issues
breakingVersion 3.0.0 removed all functionality and methods related to the Legacy Intelligence Use Case API and the App Verify SDK. Code using these deprecated APIs will no longer work.
fix
Migrate any existing code using Legacy Intelligence Use Case API or App Verify SDK to the latest TeleSign APIs and methods. Refer to TeleSign's official documentation for updated API endpoints and recommended practices.
affects: >=3.0.0
breakingVersion 4.0.0 introduced support for a new Intelligence Cloud endpoint. While backward compatibility might exist for some older endpoints, relying on previous Intelligence Cloud implementations after this update may lead to unexpected behavior or require refactoring to use the new endpoint.
fix
Review TeleSign's documentation for Intelligence Cloud to ensure your implementation utilizes the latest recommended endpoints and patterns introduced in v4.0.0.
affects: >=4.0.0
gotchaThe PyPI package name is `telesignenterprise`, but the primary Python package to import from is `telesign`. Importing directly from `telesignenterprise` will result in an `ImportError` for core modules like `rest` or `util`.
fix
Always use `from telesign import ...` for importing modules and classes, for example `from telesign.rest import RestClient`.
affects: All versions
gotchaOlder versions of the SDK (e.g., prior to 4.0.1 and 3.0.1) had issues with `pkg_resources` in newer Python environments, potentially leading to build or runtime errors related to setuptools.
fix
Ensure you are using `telesignenterprise` version 4.0.1 or newer to avoid `pkg_resources` related issues, especially when working with modern Python environments and `setuptools` versions.
affects: <3.0.1, <4.0.1
Errors
Common errors & fixes
ModuleNotFoundError: No module named 'telesignenterprise'
The 'telesignenterprise' package is not installed in the Python environment where the script is being executed.
fix
pip install telesignenterprise
Authentication Failed
The 'customer_id' or 'api_key' provided to the TeleSign client are incorrect, expired, or do not have the necessary permissions for the requested operation.
fix
Verify that your 'customer_id' and 'api_key' are correct and active in your TeleSign account dashboard, and ensure they are passed correctly to the `TeleSign` constructor.
AttributeError: 'SmsService' object has no attribute 'send'
The developer is attempting to call a method that does not exist or has been renamed within the 'telesignenterprise' SDK's SmsService (e.g., using 'send' instead of 'message').
fix
Consult the `telesignenterprise` documentation or examples to use the correct method name and parameters, typically `telesign.sms.message(phone_number, message, message_type)`.
Invalid Phone Number
The phone number provided to the TeleSign API (e.g., for SMS or Verify) is malformed, missing, or does not adhere to TeleSign's required E.164 format.
fix
Ensure the phone number is provided in a valid E.164 format (e.g., '+12135550123') and is not empty.
Upgrade
Version history
4.1.0latest on PyPI · released Jul 22, 2026
Audit
Dependencies

No dependency data recorded yet.

Agent activity
26 hits · last 30 days
node
22
OpenAI (training)
1
Resources
telesignenterprise — pip install telesignenterprise · libregistry