Hi RC community,

I had a question around rate limits and issuing new access tokens.

I've recently started running in to an issue where newly issued access tokens have 0 calls remaining in the rate limits. So after someone connects the integration, if I try and make API calls, they are rate limited straight away.

As I understand, rate limits are per user per app/integration, right? So a newly issued access token for a user should definitely not be at 0 remaining calls from a rate limit perspective, right?

For a bit of extra context, when someone connects the integration, I need the user to have the permissions to get a list of all phone numbers (https://developers.ringcentral.com/api-reference/Phone-Numbers/listAccountPhoneNumbers). So I need to make that call, to validate that the user has the right permissions, before saving the credentials and enabling the integration. But when I call that for the newly issued access token, I get the following headers:

X-Rate-Limit-Group: heavy

X-Rate-Limit-Limit: 10

X-Rate-Limit-Remaining: 0

X-Rate-Limit-Window: 60

Retry-After: 60

Anyone have an ideas here?

Thanks,
Phil