Authy Two-factor Authentication Quickstarts
As of November 2022, Twilio no longer provides support for Authy SMS/Voice-only customers. Customers who were also using Authy TOTP or Push prior to March 1, 2023 are still supported. The Authy API is now closed to new customers and will be fully deprecated in the future.
For new development, we encourage you to use the Verify v2 API.
Existing customers will not be impacted at this time until Authy API has reached End of Life. For more information about migration, see Migrating from Authy to Verify for SMS.
Two-factor Authentication Quickstarts
Our web programming language quickstarts build out our example application which incorporates Two-factor Authentication across four channels: SMS, voice, soft token, and push authentication. Note that soft token and push authentication demos will require the Authy app.
- Node.js Two-factor Authentication Quickstart
- Java (Servlets) Two-factor Authentication Quickstart
- Java (Spring) Two-factor Authentication Quickstart
- Ruby on Rails Two-factor Authentication Quickstart
- Python (Django) Two-factor Authentication Quickstart
- Python (Flask) Two-factor Authentication Quickstart
- PHP (Laravel) Two-factor Authentication Quickstart
- .NET Core C# Two-factor Authentication Quickstart
What's Next?
You can find a detailed description of all of the concepts and code in our Authy API Reference. Got two-factor properly protecting your quickstart app? Twilio will help you with your complete account security flow. Verify users have the number they claim or look-up phone number carrier and type.
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 by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.
