Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Verify Push SDK Beta

Verify Push is currently in Beta. If you're interested in participating, please complete this form and we'll be in touch.

More details are included on this page.

What is Twilio Verify Push SDK?

Twilio Verify Push SDK helps you verify users by adding a low-friction, secure, cost-effective, "push verification" factor into your own mobile application. This fully managed API service allows you to seamlessly verify users in-app via a secure channel, without the risks, hassles or costs of One-Time Passcodes (OTPs).

This new verification method includes improved privacy, security, control, and ease of implementation. Learn how Transferwise is successfully using an earlier version of this feature.

Participating in the Verify Push Private Beta

This is your chance to help Twilio build the right product for you.

The Private Beta period has started, with the Verify Push Android/iOS SDKs and API now available. We ask Private Beta participants to allocate ~1 week of a mobile/backend engineer's time to implement a prototype solution using the API to provide feedback.

Not only will you have a say in shaping the product, your team will get first access to new features and direct communication with Twilio's product and engineering team.

I'm interested! How do I get access?

Complete this interest form. Space is limited, so let us know your interest ASAP. We will be admitting applicants on a rolling basis.

Get started with Verify Push


How will my users experience Verify Push SDK?

Watch this walkthough of how Transferwise added push verification into their mobile and web apps. This is just one example - your own user experience is completely customizable.

How does Verify Push SDK work?

It works by turning your user's Android/iOS devices into a secure key via public-key cryptography.

Which verification use cases can Verify Push SDK replace SMS/Voice OTP?

Verify Push SDK can replace SMS/Voice OTP for all Authentication use cases, but not Account Creation & Recovery use cases. How much each use case contributes to your overall verification volume varies widely depending on your product’s design and usage patterns.

Verify Push Use Cases

What if my product doesn't have a mobile app?

Based on popular demand, we're starting with the SDK version of Verify Push for adding push verification to a customer's own mobile app.

We do plan to release Verify Push for the Authy app in the future, including support for the Authy Desktop app for users who don't have a smartphone. Interested? Fill out this form to let us know and stay informed on our newest releases.

What’s the difference between Verify Push and Authy push authentication?

In general, Verify Push is our newer, better version of Authy "OneTouch" push authentication.

We named Twilio Verify Push SDK to reflect how this new feature fits into the overall Twilio product taxonomy below. Twilio Authy is shown for comparison.

  • Verify - API platform
    • Push - verification factor/channel name
      • SDK - client SDK option for integration into 3rd-party app
      • for Authy app - integration into Twilio Authy app (available in future)
  • Authy - API platform
    • OneTouch - existing push verification factor/channel into Authy App
  • Authy app - free consumer mobile/desktop authenticator app

The new version enables a similar end-user experience, but we've dramatically improved privacy, security, control, and ease-of-implementation. We’ve taken all the learnings from customers using Authy in the real world and re-imagined the product from the ground-up. It's under the Verify name to indicate that the new version is built on the Verify platform, our single, omnichannel API for developers to add user verification across SMS, Voice, Email, and now Push channels going forward.

Note: Verify Push is not replacing the Twilio Authy authenticator apps, and will integrate with them in the future.

Here is a non-exhaustive list of improvements included in Verify Push:

  • No PII required. Authy requires the user’s phone # and email. Some customers were not comfortable asking for / providing this PII data.
  • More control of user identity. With Authy, the end user controlled their own user identity (Authy ID), which was shared across Authy API customers. This meant that a customer couldn’t update their user’s phone number if it changed - the user had to go through Authy’s phone change process themselves. With Verify Push, customers create and control their users identities.
  • More control of registered devices. Verify Push lets customers remove a registered device or send a Challenge to a specific registered device. This is not possible with the current version of the Authy API.
  • Improved developer experience. Verify Push SDKs are smaller than their Authy predecessor and are available as inspectable code libraries.

Are you going to deprecate Twilio Authy OneTouch?

Authy OneTouch will continue to be available for new implementations and be supported for the forseeable future.

We understand that some customers will still prefer Authy OneTouch to Verify Push for the Authy App for its built-in account recovery features and seamless device registration with phone number matching. Not sure which implementation is right for you? Get in touch, we're happy to talk through your options.

Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd browsing the Twilio tag on Stack Overflow.