This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

Information: For more information, visit the TeleSign website or the TeleSign Developer Portal.

Author: Telesign Corp.

TeleSign Web Services: Python SDK

TeleSign web services conform to the REST Web Service Design Model. Services are exposed as URI-addressable resources through the set of RESTful procedures in our TeleSign REST API.

The TeleSign Python SDK is a set of software development tools— a Python Library that wraps the TeleSign REST API, and it simplifies TeleSign application development in the Python programming language. The SDK software is packaged as a Python module called telesign.api, and is distributed as a Python Software Package using the Python Package Index (PyPI).

The Python Classes

With just three classes, telesign.api abstracts much of the complexity of the TeleSign REST API.

Python Class Description
telesign.api.PhoneId

The PhoneId class exposes four services that each provide information about a specified phone number.

standard
Retrieves the standard set of details about the specified phone number. This includes the type of phone (for example, land line or mobile), and its approximate geographic location.
score
Retrieves a score for the specified phone number. This ranks the phone number’s “risk level” on a scale from 0 to 1000, so you can code your web application to handle particular use cases (for example, to stop things like chargebacks, identity theft, fraud, and spam).
contact
In addition to the information retrieved by standard, this service provides the name and address associated with the specified phone number.
live
In addition to the information retrieved by standard, this service provides actionable data associated with the specified phone number.
number_deactivation
In addition to the information retrieved by standard, this service provides information on number deactivation for the phone number provided.
telesign.api.Verify

The Verify class exposes three services for sending users a verification token (a three to five-digit number). You can use this mechanism to test whether you can reach users at the phone number they supplied, or you can have them use the token to authenticate themselves with your web application. In addition, this class also exposes a service that allows you to confirm the result of the authentication.

You can use this verification factor in combination with username and password to provide two-factor authentication for higher security.

call
Calls the specified phone number and uses speech synthesis to speak the verification code to the user.
sms
Sends a text message containing the verification code to the specified phone number (supported for mobile phones only).
status
Retrieves the verification result. You make this call in your web application after users complete the authentication transaction (using either a call or sms).
telesign.api.Telebureau

The Telebureau class exposes services for creating, retrieving, updating and deleting telebureau fraud events. You can use this mechanism to test whether you can reach Telebureau services.

create
Creates a Telebureau event corresponding to supplied data.
retrieve
Retrieves the fraud event status. You make this call in your web application after completion of create/update transaction for a Telebureau event.
delete
Deletes a previously submitted fraud event. You make this call in your web application after completion of submit/update transaction for a Telebureau event.

Installation

With Easy Install installed, simply type easy_install telesign at the command prompt. Alternatively, you can download the project source, and execute python setup.py install.

Python Code Example: To Verify a Call

Here’s a basic code example.

>>> from telesign.api import Verify
>>> phone_number = "13103409700"
>>> cust_id = "FFFFFFFF-EEEE-DDDD-1234-AB1234567890"
>>> secret_key = "EXAMPLE----TE8sTgg45yusumoN6BYsBVkh+yRJ5czgsnCehZaOYldPJdmFh6NeX8kunZ2zU1YWaUw/0wV6xfw=="
>>> verify = Verify(cust_id, secret_key)      # Instantiate a Verify instance object,
>>> result = verify.call(phone_number, verify_code=1234)  # and use it to call the "call" method.
>>> print result.data

{u'status': {u'updated_on': u'2015-04-23T21:28:06.837153', u'code': 103, u'description': u'Call in progress'}, u'errors': [], u'verify': {u'code_state': u'UNKNOWN', u'code_entered': u''}, u'sub_resource': u'call', u'reference_id': u'DGFDF6E11AB86303ASDFD425BE00000657', u'resource_uri': u'/v1/verify/DGFDF6E11AB86303ASDFD425BE00000657'}

For more examples, see the Documentation section below.

Authentication

You will need a Customer ID and API Key in order to use TeleSign’s REST API. If you are already a customer and need an API Key, you can generate one in TelePortal. If you are not a customer and would like to get an API Key, please contact support@telesign.com.

Documentation

You will need sphinx installed to generate the documentation. Documentation can be generated by running python setup.py doc. Generated documentation can be found in the doc/build/ directory.

Detailed documentation for TeleSign™ REST APIs is available in the Developer Portal.

Testing

The easiest way to run the tests is to install nose 1.3.6 (easy_install nose) and run nosetests or python setup.py test in the root of the distribution. Tests are located in the test/ directory.

Support and Feedback

For more information about the Phone Verify and PhoneID Standard services, please contact your TeleSign representative:

Email: support@telesign.com

Phone: +1 310 740 9700

Release History

Release History

1.2.3

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.2.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.2.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.1.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.1.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.1.0

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.0.6

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

1.0.4

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
telesign-1.2.3.tar.gz (19.4 kB) Copy SHA256 Checksum SHA256 Source Oct 26, 2016

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting