Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Turn off Rate limit on REST API calls

Is it possible to turn off rate limits ( ) for certain user off? We have integrated automatic sonar analysis on pull requests we create via bitbucket using REST API for one specific user . However the problem is that with more projects we are integrating we are experiencing problems with rate limits for the given account .

Would the creation of multiple user accounts used for this purpose solve this problem? Or is this "global" limitation no matter which users invoke the call? Is it somehow possible to turn this limitation off? 

1 answer

0 votes
Ana Retamal Atlassian Team May 15, 2018

Hi Jozef! Those limits are set per user account and it's not possible to turn them off as their purpose is to keep the health of our platforms and prevent abuse. 

If you create a separate user account for some of the projects, each of the accounts will have separate rate limits so you'll be able to run more tasks simultaneously.

Hope this clarifies your question!


Is there any will to fix this? As it stands right now bitbucket cloud is not designed well for medium/large companies for CI\CD because of this limitation

I would gladly by more to increase the rate limit of the user my build server and sonar server uses- not turn off just increase!

Trying to create and balance multiple users to get around quota limits is not a very professional solution!

Like # people like this

Agreed! Would gladly pay for more quota for a single user than have to manage multiple users

Like # people like this

Any workaround to fix this?

Hi Vivekanand and others,

I would love to hear the use cases where an increased number of API calls is necessary. The most common use for large amounts calls is typically seen when CI is polling Bitbucket for changes, however, we've since released webhooks that allow Bitbucket to notify CI of a change rather than the CI having to constantly, and often wastefully, poll Bitbucket for the changes. Read more about Webhooks vs Polling here.

With the above major hurdle of CI integration solved, what other needs do you have for bulk API calls?

- Michael

we have a few services which modify git files directly. Also our CI system notifies the build status etc., to bitbucket.


We seem to be hitting this limit on a daily basis. Any workarounds would be really helpful. Would be glad to pay to increase quota than manage multiple users.

Hi Michael

My use case is

  • Multiple repositories
  • Each repository has multiple deployments
  • Each deployment has 3 or 6 variables (6 variables for our production deployments)
  • These variables contain temporary AWS authentication variables that need to be updated every 12 hours

So my script has to retrieve deployments, retrieve variables and update variables and I am hitting the rate limit.

+1 ..medium to large org here.. would gladly pay more to remove or increase limits! There should be an option that can be set so that service account users (non humans) using the bitbucket api can have higher rate limits.  It is ridiculous that we have to create multiple users as a work around does that protect your api from high rate limits? if someone can just create multiple users to circumvent this?

hi @Michael Walker

We are using to manage our CICD and GitOps flow. Jenkins X lighthouse keeper module polls, open pull request and other /repositories/ request path every second or so. Adding 10+ projects or so this would hit the 1000 per hour limit pretty quickly. Jenkins X also uses webhooks but in a different capacity. If you want to build closely integrated tooling around your git workflow, then there is a likelyhood people are are going to hit this limit pretty quickly especially in larger corporate organisations . Agree with the above comment, we will probably just add more users to circumvent this but is there must be a better/smarter way to manage this? Maybe the resource quote ?

Remember, “Don’t #@!% the customer” ;)


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

875 views 16 11
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you