Refresh Access token gives invalid client_id randomly

We have an app that is published on the marketplace for around a year now. Things have been working as usual until now, but recently we noticed that when we refresh an user’s access token we get an invalid_client error. We have not changed our client_id and client_secret since release.

This error happens sporadically and we can’t identify any pattern for why it occurs. It would be great if someone can explain why we receive this error.


“reason”: “Invalid client_id or client_secret”,
“error”: “invalid_client”

Which App Type (OAuth / Chatbot / JWT / Webhook)?

Which Endpoint/s?<refresh_token>

This JUST happened to us too at Mar 25, 2021 5:50:14 AM UTC - when retried, the token refreshed successfully.

In our case multiple requests failed between Mar 25, 2021 05:00 AM UTC to 05:45 AM UTC.

Hi @user.mix @scottjg,

When you run into this issue, can you share an example token that threw the error with us at Someone from our team will be happy to further investigate.


Hi @will.zoom ,

Thanks for the response. I have emailed with the details of an user who received the error.

Kindly help to investigate.

Thanks @user.mix,

We will be in touch shortly.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.