The Authy API is deprecated
Authy API
Deprecated, no date
The provider has deprecated the Authy API on api.authy.com without a shutdown date. It has reached End of Support and is closed to new customers, while existing customers are not yet impacted until the API reaches End of Life. When fully deprecated, calls to the API will fail.
What to use instead of these calls
Move to the Verify v2 API at verify.twilio.com/v2/Services/{}/Verifications. This transition takes more than changing an identifier, as Verify v2 requires setting up a new service and authenticating with Twilio credentials and a Verify Service instead of an Authy API key.
Verify v2 authenticates with Twilio credentials and a Verify Service, not an Authy API key; it needs a new service set up.
In Authy API's words
Authy API has reached End of Support. It is closed to new customers and existing customers will not be impacted until the API reaches End of Life and is fully deprecated.
Facts
- API
- Authy API
api.authy.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Authy API's own pages
Questions
When does this change take effect?
Authy API deprecated these calls without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Authy API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.