We're excited to announce that our Verify API now offers Voice and Flash Call as channels for sending 2FA codes. The new features supported are:
With these new features, we introduced some changes to the verification API while doing our best to maintain backward compatibility. Users who have already integrated with the API should read the release notes carefully and make the appropriate planning to accommodate the changes.
In the code snippets below, existing features are in green, while new features are in red.
After this release, the old style create payload to /v2/verify_profiles will still be accommodated and the response will remain unchanged. However, we encourage users to migrate to the new API.
After this release, the old style update payload to /v2/verify_profiles/[PROFILE_ID] will still be accommodated and the response will remain unchanged. However, we encourage the user to migrate to the new API.
Triggering a verification to /v2/verification with the old payload is still accommodated. However, the new style of API will support /v2/verifications/{channel of delivery}.
We encourage users to migrate to the new API to use the new style API features
After this release, old style and new style usage for this feature remain the same.
After this release, old style list payload to /v2/verify_profiles will still be accommodated and the response will remain unchanged. However, We encourage users to migrate to the new API to use the new style API features.
After this release, the old style and new style request remains the same. However, there are new fields added to the response.
After this release, old style and new style requests remain the same. However, there are new fields added to the response.there are new fields added to the response.
After this release, old style and new style requests remain the same. However, there are new fields added to the response.
After this release, old style and new style usage remain the same. However, there are new fields added to the response.