Details
-
Suggestion
-
Resolution: Unresolved
Description
It would be nice if we could increase the rate limits to a certain level which would allow tools such as Bamboo that polls Bitbucket frequently on repositories and their branches to not hit our rate limits.
Edit:
Bitbucket implements an API rate limit as documented here in order to protect itself against intentional and unintentional abuse. We do actively review the ideal limits themselves to balance the health of the platform with the allowances that we give our customers so these limits are subject to change, including increasing the limits for customers. If you are hitting our API rate limiting though, we highly encourage you to implement industry best practices of handling the 429 response and proceeding accordingly.
Implementing 429 retries and throttling for API rate-limits
Catching errors caused by rate limiting
If there are use cases where handling the 429 response is not possible/feasible, please share these so that we can properly address these use cases.