Verify API - Get started with Push Verify
NOTE:
Contact our sales team for availability of Push Verify in your region. This product is available for full-service accounts only.
This page explains the basic usage of the Push Verify verification method of the Telesign Verify API and directs you to two key sets of instructions you will need to code your integration. These instructions assume the use of a verification policy with:
- Push Verify set as the primary verification method.
- SMS one-time passcode (OTP) set as the fallback verification method.
These instructions assume a log in use case, but the same verification workflow also applies to other use cases.
Before you begin
Install the Telesign Verify Android SDK. Contact Telesign Customer Support or your Telesign contact to get access.
Basic usage
This workflow assumes that each step in the flow is successful and that the app has not already registered for Push Verify.
- User downloads and installs your mobile app on their device for the first time. This app includes the Telesign SDK.
- You register this new device with Push Verify.
- The user later attempts to log in on your website.
- You begin to authenticate that user by sending a push to their registered device.
- The user approves the push on their device.
- Your website allows the user to log in.
NOTE:
Android Verify SDK events for the Push Verify verification method are sent as responses to SDK methods. You do not need to subscribe to these events.
Setup
- Add the Telesign Verify Android SDK as a dependency in the Gradle project for your Android app.
- Add the following statements to the "proguard-rules.pro" file for the project:
These statements exempt those two classes from being obfuscated by ProGuard, which is necessary for the Telesign SDK to function.
-keep class com.telesign.verify.data.dto.** { *; } -keep class com.telesign.verify.api.models.** { *; }
Further instructions
For further details on how to implement the different components of this architecture, see:
Updated about 1 month ago