I ran into an issue with setting up the Oauth stuff with Quickbooks. Parabola’s redirect url is registered with my app, I have the client_id and client secret for the production account. Not sure where I am supposed to use the client secret key. It’s also not clear what the endpoint for API calls is or how the userinfo endpoint is used during the token retrieval process. Could you guys maybe point me in the right direction and maybe I’ll write up a basic tutorial once it’s figured out.
I’ve tried this one a number of times with no success. I think there is something undocumented on their end that is happening that does not play nicely with our OAuth implementation.
I read somewhere in their forums that the client_id is sent with the private key like {client_ID}:{private key} I also saw a reference to the info being returned from the user info endpoint during the get token process.
Hi @Francis_Costello - not yet on our end, we’ve also been stumped on this and invite any Community members to share their input if they’ve discovered additional information.
Feel free to share this with the GuickBooks Learn & Support Team and ask if there’s a misunderstanding about their OAuth implementation. They might be able to clarify why it doesn’t work with Parabola’s OAuth method.
The OAuth settings requests are application/x-www-form-urlencoded by default, and the data fetching requests are application/json by default. The headers should be inserted automatically!
I’m stumped why integration with Quickbooks Online is not a priority? Parabola has never worked with Quickbooks Online. As someone who’s spent hours trying to get this to work, it’s immensely frustrating that this is pushed off as “not our fault.” Isn’t Quickbooks Online is large enough to make this work with a workaround from Parabola?