Recently we have been getting a lot of trouble when trying to implement the API of Exact Online. We often get a response with a 401 error indicating there is something wrong with the refresh token.
I have contacted support of Exact and they indicated that the refresh token rules have been getting more strict lately.
This article shows how they plan to limit the usage of refresh tokens in the API, the literal answer I received was:
A token is valid for 600 seconds.
You can use the token for different calls and you don’t have to request a new token for every call.
Only when 570 seconds have passed can you reqeuest a new token with the refresh token.
In N8N I get a 401 error almost immediately. I can manually go to the ‘Credentials’ and obtain a new Access Token, however, when I perform the second request, it immediately seems to give me this error.
Could we please take a look at this?