Verify Push is in Public Beta.
The data model does not require any PII (such as phone or email).
- Service: an organization or environment (e.g. stage, prod). Contains configurations for all verification methods available through the Verify platform (SMS OTP, Voice OTP, Email OTP, Push Verification). A Twilio [sub]account can have multiple Services. Each Service contains multiple Entities that are not shared across Services.
- Entity: a user or other identity that needs verification. An Entity can contain multiple Factors.
- Factor: a verification method, which involves an exchange of secrets via a communication channel. For factor_type push, which is based on public-key cryptography, the Factor contains the public key of the private-public keypair generated by a registered device along with its metadata. A Factor contains multiple Challenges.
- Challenge: a single verification attempt of an Entity using a Factor. A single Factor has multiple Challenges.
- Access Token: an authentication token that a client app (e.g. Android app) uses to authenticate its request to the Verify Push API when creating (i.e., enrolling or registering) an Entity and/or Factor.
- Webhook: a config that specifies that Verify Push notifies your app backend of an event.
Sample App DemoWatch
Watch this demo to see how the data model is used to register a user/device and verify a user. The demo uses a Sample App and Sample Backend. These samples are like transparent versions of a real mobile app and app backend integrated with Verify Push, but they fully expose the API calls that are being made and the data exchange behind the scenes.
Verify Push SDK involves two main sequences:
- Register user and device
- Verify a user