Refresh token automatically on HTTP 401 or 403 response?

I’m using the API (v1.0.10) in the following way:

    var oauth2Client = new OAuth2(getGoogleCredentials().clientId, getGoogleCredentials().secret);
    oauth2Client.setCredentials({
      access_token: user.services.google.accessToken,
      refresh_token: user.services.google.refreshToken
    });
    calendar.events.list({
        calendarId: 'primary',
        auth: oauth2Client
      }, ...);

When my token is expired I get an HTTP 401 back from the server. However, I’d expect the library to automatically refresh my token and make the request again. It doesn’t.

I figured out that a workaround is to add the expiry_date when calling setCredentials, e.g.

oauth2Client.setCredentials({
      access_token: user.services.google.accessToken,
      refresh_token: user.services.google.refreshToken,
      expiry_date: user.services.google.expiresAt
    });

But this isn’t mentioned in the docs. I’d expect expiry_date to be optional and the API to auto refresh the token.

[bdrazen]

Cheers for the snappy response! 🍻

[JustinBeckwith]

Greetings! The event based approach is new, and was added after this post was originally answered 😃 . Both ways are fine honestly. The nice thing about using the event is that you get notified not only when the refresh_token changes, but also when the access_token is refreshed. The tokens returned here should return the expiry_date.