Found this bitbucket article that API rate limits headers should be present for mostly all repositories/2.0 endpoints:https://www.atlassian.com/blog/bitbucket/introducing-scaled-rate-limits-for-bitbucket-cloud-apibut they are missed. i want to increase the API rate limits based on that, because now we are using 1000 requests per hour and its absolutely not enough for us.what can you suggets?
Hi @Jack_s Account ,
Make sure you are accessing the APIs using requests made via Access Tokens and Forge <span>asApp</span> API requests, otherwise the scaled rate limits do not apply.
<span>asApp</span>
Unfortunately, as far as I know (being following this issue closely for a long time now), there is no way to increase the rate limits.
You might find this ticket useful, as there are some discussions on workarounds before the scaled rate limits feature was implemented.
@Saxea _Flowie_ i tried different auth types (Oauth, api key) and there are no such headers in any case.i don't know how to handle it properly, because i want to avoid "1000 requests per hour" . i want to be sure i can implement retry logic in case i got "429 err" if there is such err in bitbucket.or get it from headers, or smth else.in bitbucket on premise its possible to get rate limit parameters from API.
Hey @Jack_s Account
Rate limits apply per account, so if you need more than 1,000 requests per hour, I suggest is to use two or more account authentications, such as App Passwords. Then, distribute the requests between these accounts to help you avoid exceeding the 1,000-request limit per account.
Regards,Syahrul
It looks like you're new here. Sign in or register to get started.
