Skip to content
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

Api Key Support #45

Open
jonsgreen opened this issue Oct 1, 2018 · 4 comments
Open

Api Key Support #45

jonsgreen opened this issue Oct 1, 2018 · 4 comments

Comments

@jonsgreen
Copy link

Any thoughts of supporting api keys in preparation for 6.0?

@wingrunr21
Copy link
Owner

I'm not currently using this gem in production. If someone else wants to submit PRs or step in to maintain it I'm all for it.

I also still don't have publish rights to the gem on RubyGems so would need to get that figured out as well.

@timnovinger
Copy link

We're currently using this gem in production and could sure use the update.

Does anyone know when the API version change is actually scheduled to take place? I don't see anything in the docs other than it is essentially "coming soon".

@jonsgreen
Copy link
Author

@timnovinger I have a working version locally but I was having problems with some critical endpoints so I am waiting for those to be fixed. Here is the latest info I got from MindBody support:

"I have submitted the issue to our Development Team for further investigation under Work Item "607708 - API - CancelSingleClass (V 5.0, 5.1) - does not work when passing API-key in header. You must pass Source Credentials in Body of the REQUEST". You will receive a reply to this email when the issue has been resolved. "

Given that these critical endpoints have not been worked out my sense is that 6.0 is not imminent.

@jonsgreen
Copy link
Author

@timnovinger also, I will try to submit a PR once these issues are cleared up.

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

No branches or pull requests

3 participants