-
Notifications
You must be signed in to change notification settings - Fork 49
Migrated OTP api to Verify api #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
README.md
Outdated
# otp_verify requires a recipient, a token as required parameters, and other optional paramaters | ||
client.otp_verify(31612345678, 123456, {:reference => "YourReference"}) | ||
# verify_token requires the id of the verify request and a token as required parameters. | ||
client.verify_token(31612345678, 123456) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First argument must be a verify id instead the phone number I guess
Hey 👋 thanks for working on this PR. Do you guys have any plan to have it merged soon? |
Hey, any update on this? We need the verify functionality. If there is anything missing, we are willing to help to get this merged |
thanks! can you also publish a new version (on github and rubygems) =) |
@p0wl 👍 |
is there a way to test the verify API with a |
@p0wl I don't think so but shoot an email to our friends at [email protected] and they can tell you for sure. |
@samwierema breaking changes since the OTP Api doesn't exist anymore.