You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned here, it seems not possible to automate the way we can get authorization code, before getting access token and refresh token (which is taken into account thanks to get_bearer_token method). This is an issue for browserless, server side solutions interacting with intuit quickbooks API.
Since the refresh token doesn't last more than 1 day (the 100 days was never guaranteed), is there a planned solution for this ? Thanks a lot !
We've been using the refresh token with no issues but we only have one instance. If you scale to multiple instances or you use lambda functions unfortunately the only way to handle this without requiring scraping the QB webapp is to have a distributed database with the valid refresh token and an atomic control on the token access and renewal.
Thanks for the suggestion! Today we do require an admin user to explicitly consent, through the Intuit authorization page, before an application is able to access data.
Refresh tokens last for 100 days and are on a rolling expiry. As long as you refresh the token at least once every 100 days, you can utilize these till their maximum lifetime for gaining new bearer (access) tokens.
Activity
dantebarba commentedon Jan 27, 2022
@mNemlaghi did you find a solution to this?
daccorti commentedon Apr 27, 2022
@mNemlaghi Also interested if you solved this issue.
@IntuitDeveloperRelations - Do you have any recommendations for this?
bdsoha commentedon Jul 20, 2022
@mNemlaghi Any updates? This would be a great feature for server-side applications and lambda-functions.
An4ik commentedon Jan 10, 2023
We've faced the same issue but did some tricks to solve it:
So based on documentation documentaion hope this will work
Donny-GUI commentedon Jan 13, 2023
i ended up just using selenium headless
aaldaghar commentedon Jul 4, 2023
Is there no plan to fix the authorization code issue?
dantebarba commentedon Jul 4, 2023
We've been using the refresh token with no issues but we only have one instance. If you scale to multiple instances or you use lambda functions unfortunately the only way to handle this without requiring scraping the QB webapp is to have a distributed database with the valid refresh token and an atomic control on the token access and renewal.
bdsoha commentedon Jul 5, 2023
Do you mind sharing the code you used?
robert-mings commentedon Aug 1, 2024
Hi @mNemlaghi,
Thanks for the suggestion! Today we do require an admin user to explicitly consent, through the Intuit authorization page, before an application is able to access data.
Refresh tokens last for 100 days and are on a rolling expiry. As long as you refresh the token at least once every 100 days, you can utilize these till their maximum lifetime for gaining new bearer (access) tokens.
cc: @dantebarba, @daccorti, @bdsoha, @An4ik, @Donny-GUI, @aaldaghar.