Skip to content

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

Merged
merged 6 commits into from
Apr 25, 2018
Merged

Conversation

dysosmus
Copy link
Contributor

@dysosmus dysosmus commented Dec 6, 2017

@samwierema breaking changes since the OTP Api doesn't exist anymore.

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)

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

@cristiangreco
Copy link

Hey 👋 thanks for working on this PR. Do you guys have any plan to have it merged soon?

@p0wl
Copy link

p0wl commented Apr 25, 2018

Hey, any update on this? We need the verify functionality. If there is anything missing, we are willing to help to get this merged

@marcelcorso marcelcorso merged commit 8d51637 into master Apr 25, 2018
@p0wl
Copy link

p0wl commented Apr 25, 2018

thanks! can you also publish a new version (on github and rubygems) =)

@marcelcorso
Copy link
Contributor

@p0wl 👍
releasing is on @samwierema's hands.

@p0wl
Copy link

p0wl commented Apr 26, 2018

is there a way to test the verify API with a test_ api token? like a fixed otp that always works?

@marcelcorso
Copy link
Contributor

@p0wl I don't think so but shoot an email to our friends at [email protected] and they can tell you for sure.

@marcelcorso marcelcorso deleted the migrated-otp-to-verify branch April 26, 2018 19:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants