I'm stepping over my line of experience as I do regularly...
Trying to build a private app for Mindbody Online (https://developers.mindbodyonline.com/PublicDocumentation/V6#authentication) but the authentication is killing me.
Somebody told me he's also done it with Session Auth, but I'm fouling that up somehow. Pointers would be greatly appreciated, or if someone had time to do a video call for an hour or so, I'd gladly pay for you time.
Best answer by BowTieBotsView original
@ikbelkirasan who's an expert at such things!
Can you post what your current authorization code so we can troubleshoot where the error might be.
Authorization is set up as follows:
And I have created functional webhooks with just the API and siteID, so I'm just messing something up somewhere along the line.
@BowTieBots and @AndrewJDavison_Luhhu
Change your inputs to the following example and pay close attention to the case as the values are case sensitive.
Set up step 2 so it looks like this:
Set up step 3 so it looks like this:
For Easy Reference here are all the values:
Let me know if you have any more questions.
Thanks for stepping through this with me.
Session Auth is the correct type. The initial request returns the "staffUserToken" that you need in the rest of your API calls. API Auth wouldn't allow for that storage.
It looks like the API is looking for the username and password in the URL Params instead of the body. Change step 2 to look like this:
If you get any more errors can you post the error log from Monitoring please. It gives a lot for detail than Zapier's error response in app.
I'm not getting any more detailed information than this.
But it's still giving me an error
If you're still getting the error, make sure you don't set the Authorization header when you call /usertoken/issue because this might be the reason why that error occurred. You can check the chart for when 4xx errors occurred and check if the Authorization header was set when it was requesting a new access token. Hope this helps!
@Robert_Segelquist, we just wanted to check-in to see if you were able to get things solved here and if any of the previous suggestions helped to solved your issue. If so, you can mark that it "answered your question". If not, let us know and we can continue looking into this with you!