How telesign/python_telesign works
TeleSign Self-service Python SDK lets application developers call TeleSign messaging, voice, phone-data, and risk APIs. The main workflow is an application selecting a domain client, submitting a request, and receiving the REST response; messaging and voice also expose status lookups. Domain clients use a shared REST layer for authentication and HTTP transport. Utility functions additionally support callback-signature verification and common formatting or randomness tasks. The README confirms SDK-managed authentication; sampled source shows request signing and domain methods, but omits parts of REST execution.
Main entry points: rest.py REST Client · messaging.py Messaging Client · voice.py Voice Client · phoneid.py PhoneID Client
Components 8
Communications
- Messaging Client
telesign/messaging.py - Voice Client
telesign/voice.py
Phone And Risk
- PhoneID Client
telesign/phoneid.py - Score Client
telesign/score.py
REST Transport
- REST Client
telesign/rest.py
Utilities
- Helpers
telesign/util.py
Other components
- Application
- TeleSign API
Connections 11
- Application → Messaging Client: calls
- Application → Voice Client: calls
- Application → PhoneID Client: calls
- Application → Score Client: calls
- Messaging Client → REST Client: POST/GET
- Voice Client → REST Client: POST/GET
- PhoneID Client → REST Client: POST
- Score Client → REST Client: POST
- REST Client → TeleSign API: sends requests
- TeleSign API → REST Client: returns responses
- Application → Helpers: uses helpers