ST-2026-226 · API endpoints & versions
Atlassian has removed the native Bitbucket Cloud Issue tracker API endpoints
Atlassian states that the API endpoints supporting Bitbucket Cloud's native Issue Tracker were fully removed on 20 August 2026, completing the previously announced native Issues retirement for that endpoint family.
Previous state
Bitbucket Cloud integrations could call API endpoints that supported the product's native Issue Tracker while that legacy feature remained available.
Current state
Atlassian states that the API endpoints supporting the native Bitbucket Cloud Issue Tracker are fully removed.
Affected users
Who needs to care
Developers and integrations that still depend on Bitbucket Cloud's native Issue Tracker API endpoints.
Required response
What to do
Remove dependencies on the retired native Issue Tracker endpoints and migrate issue-tracking workflows to a supported alternative before making further API calls.
Evidence boundary
What the source does not prove
Atlassian proves removal of the native Issue Tracker endpoint family. It does not retire Bitbucket Cloud itself, remove unrelated Bitbucket APIs, or withdraw the separately documented Basic and Bearer authentication options for API tokens.
Lifecycle history
Dated event sequence
- Issue Tracker API endpoints fully removed
Atlassian announced that the API endpoints supporting the native Bitbucket Cloud Issue Tracker are now fully removed.
Evidence ledger
First-party sources
- 01Atlassian — Bitbucket Cloud developer changelog
Official Atlassian Bitbucket Cloud developer changelog · 2026-08-20
Open official source ↗