LinkedIn API: The token used in the request has been revoked by the user

3
votes

We have integrated LinkedIn for the automation using OAuth2.0 3-legged authentication method. It was working fine earlier but now, our users are getting the following issue:

"The token used in the request has been revoked by the user"

Issue Details: Our code, programmatically generates a new access token for the authenticated user with using the refresh token and when it gets fired in the next API call, our users are getting the above error. But, it starts working after 3 to 5 min.

Note: Our system uses refresh token to get the access token in each API call of the LinkedIn endpoint.

Error:

{ "serviceErrorCode": 65601, "message": "The token used in the request has been revoked by the user", "status": 401 }

Kindly, look into this matter and provide a quick solution except the delay after generating the token.

1
linkedinlinkedin-api
Did you find the reason ?, I get this error too. - K-s S-k
Getting this issue as well. Thought it was something wrong on my end but looks like it might not be - stor314
I think I was able to get it to work by setting a timeout after refreshing the token, kind of hacky but I'm not sure what else to try - stor314
@stor314, you mean this may be related to eventual consistency on LI side? What was the duration of the timeout? - Ricardo Souza
@RicardoSouza i think i set it to 5 seconds, after doing that never ran into the issue again. refresh only happens every two months so i just decided to leave it in - stor314

1 Answers

0
votes

You need to use newly created LinkedIn connection throughout your workflow(s) and LinkedIn action steps. Delete all the previous LinkedIn connections and keep using the newly created connection. The LinkedIn connection will work for an year this means that and you only need to re-authorize your LinkedIn application in your Pabbly Connect workflows after an year.

Read more: https://forum.pabbly.com/threads/troubleshooting-linkedin.2023/