Upcoming brownouts and removal of the deprecated Bitbucket Cloud code search API

Following the previous deprecation announcement, we will begin scheduled brownouts of the Bitbucket Cloud Code Search API on 3 November 2026 at 00:00 UTC.

Brownouts are temporary periods when the API is unavailable, intended to help you identify integrations that still need to migrate. The brownout duration will progressively increase before the API becomes permanently unavailable on 15 November 2026 at 00:00 UTC.

Migrate your integrations to the workspace code search API before the brownouts begin.

More details

Affected endpoints

• /2.0/users/{user}/search/code
• /2.0/teams/{team}/search/code
• /2.0/workspaces/{workspace}/search/code

Brownout schedule

All dates and times are in UTC. Brownouts start at 00:00 UTC each day and repeat every 6 hours. The duration below applies to each brownout window.

Date	Brownout duration	Start time (UTC)
November 3, 2026	15 minutes	00:00, 06:00, 12:00, 18:00
November 4, 2026
November 5, 2026	1 hour
November 6, 2026
November 7, 2026	2 hours
November 8, 2026
November 9, 2026	3 hours
November 10, 2026
November 11, 2026	4 hours
November 12, 2026
November 13, 2026	5 hours
November 14, 2026
November 15, 2026 onwards	Permanently unavailable

During brownouts, requests to the affected endpoints will return HTTP 410 Gone, with an error message linking to the replacement API documentation. Outside the scheduled brownout windows, the deprecated endpoints will remain available until permanent removal.

Required action

Update applications, scripts, and integrations that use the affected endpoints to use:

POST /2.0/workspaces/{workspace}/codesearch

The replacement API uses a different HTTP method and request format, so migration requires more than changing the endpoint URL. Review the workspace code search API documentation and update your integration before 3 November 2026 to avoid disruption.

We understand these changes require effort, and we're here to support you. If you have questions, need migration guidance, or run into issues, please contact Atlassian Support.