Fitbit API calls to authorize get rate limit exceeded errors

[piotr-zywien]

Hi @JeremiahFitbit,

I am getting rate limit exceeded errors when trying to authorize users - as far as i read in the documentation, authentication is not dependent on rate limits. Did anything change? We've started getting the "courtesy" emails since this morning. It seems like it might be an issue on your side.

Please see my postman response:

By the way this also happens when refreshing the access token. Again, neither exchanging the authorization code for the access token nor refreshing the access token should be capped by rate limits.

I only refresh the access token if it expires obviously. Hence I would appreciate some assistence.

I would appreciate any help and/or for the issue to be fixed, thanks! 🙂

Sincerely,
Piotr.

[JeremiahFitbit]

@piotr-zywien: Refresh token requests are user-scoped rate limit. Code requests client-scoped rate limit. Send us a private support request with your client id and we'll increase the client rate limit since you seem to be onboarding more than 150 users an hour. Reference this topic so the support team knows the situation.