-
Notifications
You must be signed in to change notification settings - Fork 46
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
Comments
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. |
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". |
@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. |
@timnovinger also, I will try to submit a PR once these issues are cleared up. |
Any thoughts of supporting api keys in preparation for 6.0?
The text was updated successfully, but these errors were encountered: