Bitbucket Cloud Announcing End of Life for Cross-Workspace APIs: Timeline and Next Steps

[#1]

Hi everyone,

Last year, we shared our initial Changelog announcement about the sunsetting of cross-workspace APIs. We have since released the new APIs that replace the functionality we’re deprecating. After receiving some feedback from our partners, we have decided to extend the date from February 27, 2026 to March 31, 2026. Please read on for more information on the end of life for these APIs, including brownouts we will be running in the final weeks of support for the old cross-workspace APIs.

Official timelines for end of life for cross-workspace APIs

Phase 1: Release new cross-workspace APIs

Effective: Now

We have officially released the new cross-workspace APIs and are ready to sunset the old APIs.

This phase ensures that everyone using the old cross-workspace APIs has a path forward.

Phase 2: Phase out the old cross-workspace APIs in the weeks leading up to end of life

Effective: March 23, 2026

In the final week of support for the old cross-workspace APIs, we will run a series of brownouts to increase awareness of usage of the APIs. During these pre-planned times, the old APIs will temporarily be unavailable, highlighting where customers, app vendors, and partners will need to make the replacement.

If you have already switched to using the new cross-workspace APIs, your functionality will not be interrupted. We encourage all customers, app vendors, and partners to switch to the new APIs as soon as possible.

Please see the below schedule for the list of planned brownouts.

Dates	Brownout duration per window	Brownout starting windows (UTC)
March 23, 2026	120 min/2 hours	18:00
March 24, 2026	120 min/2hours	23:00
March 25, 2026	240 min/4 hours	17:00
March 26, 2026	240 min/4 hours	21:00
March 27, 2026	480 min/8 hours	16:00
March 30, 2026	720 min/16 hours	14:00
March 31, 2026	Final removal

If you are using the soon-to-be-sunset cross-workspace APIs in your workflow, app, or product, you will get a Not Found Error (404 Error Code), which could break your workflow. In the event you experience a loss in functionality, please contact the owner of your workflow, app, or product as they will need to switch to the new APIs. Please refrain from contacting Bitbucket Cloud Support unless the issue extends beyond the 404 Error Code.

Phase 3: End of life of cross-workspace APIs

Effective: March 31, 2026

As indicated in the schedule above, on March 31 we will move the old cross-workspace APIs into the end of life phase. This means that these APIs will no longer work and all integrations that rely on them will not function.

What does end of life mean?

• Endpoints are removed: Old cross-workspace API endpoints will be permanently disabled and will return errors. No further bug fixes or restores will be provided.

• Migration is required: Any app, integration, or script using the old APIs must move to the new cross-workspace APIs.

• No support or compatibility guarantees: The old APIs will be unsupported, unmonitored, and may be removed from documentation and tooling at any time.

We know that our app vendors and partners are most impacted by this change and so we wanted to share some additional information to further explain the changes.

What this unlocks

We have been making improvements to Bitbucket Cloud’s infrastructure that has required some changes. Overall, we are driving to a larger goal of making Bitbucket more reliable, more performant, and more secure for all our customers by scoping data down into a single workspace. This focus also delivers several key advantages:

• Launch data residency for Bitbucket Cloud, starting in the EU region: We plan to launch EU data residency by the end of 2026, followed by the India region.

• Upcoming support for paid Marketplace apps: We will support paid Forge apps in the future and we're actively finalizing the timelines. We'll update everyone with confirmed dates as soon as they're set.

• More reliable performance, for all enterprises: With these infrastructural changes, customers can expect to see improvements to Bitbucket’s performance and reliability.