If a phone number's score is too high for the threshhold you select (work with your Technical Account Manager to set this), you can block it.
You can find out more about Score on the following pages: The following examples demonstrate typical HTTP 1.1 Request/Response transactions for invoking the Verify SMS web service, and for retrieving the verification results.
Tele Sign generates the verification code When you send a POST request without specifying a verification code, Tele Sign generates the code value by default and sends it to the end user.
For example: If you implemented your configuration so that Tele Sign generates your codes, then you must send Tele Sign completion data using a Get Status request.
When working with an access token, you may need to check what information is associated with it, such as its user or expiry.
To get this information you can use our debug tool, or you can use the API endpoint.
When someone has de-authorized your app it should treat someone as if they are new to the app.
Speak with your TAM to purchase one or more phone numbers to use as sender ID.
If you generate your own codes, sending completion data is optional, but recommended.
(Completion data is the reference ID associated with an end user's transaction, and the verification code entered by the end user.
(These examples don't include a subcode, but subcodes are described in the error reference.) Access Token has expired If the access token becomes invalid, the solution is to have the person log in again, at which point you will be able to make API calls on their behalf once more.
The login flow your app uses for new people should determine which method you need to adopt.