Twilio Verify vs. Authy
The Verify API is a consolidated version of earlier versions of our phone verification and 2FA APIs.
We strongly encourage you to use the Verify API for all new development.
|
Product |
Description |
Channels |
|
Verify API |
Phone, email, and device-based verification, multi channel support for two-factor authentication (2FA), passwordless login. |
SMS, Voice, Email, Push |
|
Authy API |
Older version of the Verify API. Please use Verify for new use cases except those requiring Authy App push or TOTP (see FAQ). |
Authy App push or Time-based One-time Passcodes (TOTP) with SMS/Voice fallback |
|
Twilio Authy App |
|
Get started with Verify
- Verify API reference
- Serverless phone verification
- Verify Quickstarts (C#, Python, Node.js, Ruby, Java, PHP)
FAQ
Is the Authy API going away?
We plan to continue supporting the Authy API, but new development and features will be on the Verify API.
Will TOTP be supported in Verify?
Yes, our vision is to add TOTP to Verify.
Will Authy App Push be supported by Verify?
Yes, our vision is to integrate the Verify Push API with the Authy Apps.
Will other channels be supported by Verify?
Please reach out if you have other specific channel requests.
How does this affect the Twilio Authy app?
The Authy App is not going away. We are committed to growing, developing, and supporting the Twilio Authy app as a consumer application and as a complement to our work on the Verify API.
More questions?
Get in touch to discuss your application needs and how to use Twilio for account security.
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.