Hi Chayce.
Thank you for the reply.
Yes, it is Oauth2, which I think is adding to the problem. Something tells me I'm not going to be able to get this to work 😌
Thank you anyway.
Michael
I would reach out to support - I don't know how QB handles Oauth2, its not in a way that I've ever seen and I know even less about how they handle the refresh token aspect. Apologies for not being very helpful, I just haven't seen enough publicly or any changes over the past couple of years that would provide any more insight.
