nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Reckon Hosted API: Authorization has been denied for this request.

skiebask

Hi,

Our team has been diligently working with Reckon Account Host API for a month, integrating it into our sync process hourly with OAuth2 Authorization code flow and refresh token. However, we've encountered a roadblock: After one month, we received a 401 (authorization has been denied) error.

I need to know why it is an unauthorized error and the root cause of the error. However, we are using the refresh token flow, so this error should not happen in this scenario. We appreciate your potential help in resolving this issue.

Please note that we have reconnected the authorization, and it worked fine. We just need to know what caused an error and how to solve this problem.

Comments

Nickiu

Hi @skiebask,

Usually a refresh tokens expire after 1 year, When did you received this token?

https://help.reckon.com/article/xcv063pbxz-reckon-api-authorisation-services

Thanks,

Nick

skiebask

Hi Nickiu,

Thanks for reply.

Our process does an integration sync every hour. It should reconnect to get a new access token when the old one expires. Ideally, we should get a new access token and refresh it every day.

Anyway, my refresh token is not over 45 days old, as we just executed our process last month.

cosmic

Cosmic has these kind of problem now and then , the token gets expired , or we need to REAUTHORISE .

Nickiu

Hi @skiebask,

When did you first get the Authorization Code? has it been a year yet? To get refresh a token required to have a valid Absolute refresh token and the Absolute refresh token expire every 12 months. If the Absolute refresh token is expired. you will not be able to generate a new refresh token.