latest 6.2.x 6.1.x 6.0.x 5.8.x 5.7.x 5.6.x 5.5.x 5.4.x 5.3.x 5.2.x 5.1.x 5.0.x 4.18.x 4.17.0 4.16.x 4.15.x 4.14.x 4.13.0 4.11.x 4.8.0 4.7.0 4.6.0 4.5.0 4.4.0 4.2.0 4.1.0 4.0.0 3.22.0 3.21.0 3.20.0 3.19.0 3.18.0 3.17.0 3.16.0 3.15.0 3.14.0 3.13.0 3.12.0 3.11.0 3.10.0 3.9.0 3.8.0 3.7.0 3.6.0 3.5.0 3.4.0 3.3.0 3.2.0
Auto Light Dark
Auto Light Dark
latest 6.2.x 6.1.x 6.0.x 5.8.x 5.7.x 5.6.x 5.5.x 5.4.x 5.3.x 5.2.x 5.1.x 5.0.x 4.18.x 4.17.0 4.16.x 4.15.x 4.14.x 4.13.0 4.11.x 4.8.0 4.7.0 4.6.0 4.5.0 4.4.0 4.2.0 4.1.0 4.0.0 3.22.0 3.21.0 3.20.0 3.19.0 3.18.0 3.17.0 3.16.0 3.15.0 3.14.0 3.13.0 3.12.0 3.11.0 3.10.0 3.9.0 3.8.0 3.7.0 3.6.0 3.5.0 3.4.0 3.3.0 3.2.0

How to trigger a full Bitbucket rescan?

You can schedule a rescan of all data in your Bitbucket instance with a single REST call like this:

curl -u admin -X PUT https://{bitbucket.server}/rest/security/latest/status/total_rescan

where

  • admin is your Bitbucket admin user (you’ll be prompted for a password), and

  • {bitbucket.server} is the URL of your Bitbucket server.

You can monitor progress of scanning on the Global Dashboard page.

Please note that if you have a large Bitbucket instance, all existing branches in all projects and repositories will be scanned, which may be very resource-intensive and take a long time to complete.

For full documentation of this API, including changing the number of scans run in parallel, see REST API for Mass Scanning.