Are rate limits defined on a user level or for the entire workspace

[Ayush Surana]

I am facing rate limit issues multiple times across different apis. 

Following are the apis that we generally call :- 

1. Cloning
2. Fetching PR details
3. Fetching Comments on the PR
4. Posting comments on the PR

I have gone through this document https://support.atlassian.com/bitbucket-cloud/docs/api-request-limits/ and in order to avoid rate limits we created credentials across multiple users. 

But we have observed all the users being rate limited at the same time. Is the rate limit on a specific user or is it on a particular IP or for the entire workspace?

Some clarity here would be highly appreciated. 
Thanks

[Patrik S]

Hello @Ayush Surana ,

and welcome to the Community!

For authenticated calls, the rate limits are measured against the authenticated user. 

So if you have different credentials across different users, each user will have their own requests tracked separately and their own rate limit allowance.

It's important to highlight, though, that all API requests made through OAuth are treated as coming from one user, no matter who created the OAuth consumer in the workspace. This means all requests count together toward the rate limit for the account, which can cause you to hit the limit faster than expected. To avoid this, you can use repository, project, or workspace Access Tokens instead of App passwords (user-based tokens).

For more details and mitigation steps for rate limits, the following article may be of help:

• Bitbucket Cloud Rate Limit Troubleshooting 

Thank you, @Ayush Surana !

Patrik S