Issues with Missing refresh_token in API Response

[ghostxne]

I successfully set up authentication and the process to obtain an access_token, but I'm facing an issue while configuring the token refresh process. According to the documentation, the response from the API when requesting a token refresh should contain five properties: access_token, token_type, scope, expires_in, and refresh_token. However, in my case, the response contains everything except the refresh_token, which is crucial for further token refreshes.

Could the problem be related to requesting the token refresh immediately after obtaining the first access_token? How can I resolve this issue to ensure that the response includes a refresh_token for subsequent requests?

[ghostxne]

Please help me 😔🙏

[Ximzend · Accepted solution]

Hi ghostxne, welcome to the Community!

When you don't get a new refresh token after refreshing the access token, you can keep using the old one.

Let me known if this helps and if you have other questions.

[joshrichards]

Hey it would be great if this was added to the docs or if in the code example you just contained something like:

const spotifyRefreshToken = body.refresh_token || refresh_token;

It was pretty annoying to have to track this down.

[simpamusic]

i just spent i couple of hours debugging this. please update the documentation for gods sake.