Understanding what Bitbucket Cloud's rate limits are, how they are cycled, and how to work within them will help you build better integrations using API calls.
We don't limit most "normal" API requests such as:
- Get list of teams
- Get list of users
The API requests with limits are listed in the section below.
Watch this page to be notified when any change occurs to our defined API request limits.
How calls are measured
Tracking the number of calls is measured based upon if they are authenticated or unauthenticated calls as follows:
- Unauthenticated calls: measured against a specific IP address.
- Authenticated calls: measured against the user id.
Rate limits are divided into a one-hour rolling window for both authenticated and unauthenticated requests, which means that for every minute that passes, you will be provided that time to run new requests but the total you can run consecutively over an hour is 1,000.
The following table defines our API request limits:
|Git web (HTTPS://) requests||60,000 requests per hour|
|hg web (HTTPS://) requests||30,000 hgweb requests per hour|
|SSH requests (all SSH requests are rate limited)||30,000 SSH requests per hour|
Access to raw files
Raw file requests: the number of times a file is actively downloaded, including files in the download section of the site.
This is not a limit on actions such as:
|5,000 raw file requests per hour|
Archive files: .zip, .gz, and other compressed archives of your repository.
|5,000 files per hour|
Access to repositories data
Any access to /2.0/repositories/* such as:
1,000 per hour