nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Did the Bitbucket REST API change?

Denise Skidmore

We've had a pipeline running for some time that runs a code review tool and adds annotations to our PRs. It uses REST API extensively to do this. Last week it started failing. At first I thought it was something to do with the changes to auth, but I was getting an auth token. After regenerating my token my new token had more scopes, but still failed.

First hurdle wasn't too bad once I found it, my diffstat url is now coming from the PR info links

But I've got downstream errors yet to resolve. Is there a list of the API changes?

Accepted answers

All comments

Ajay _view26_

Hi @Denise Skidmore

Yes — Bitbucket Cloud has been going through a meaningful auth and API transition that explains what you're seeing.

The developer changelog at developer.atlassian.com/cloud/bitbucket/changelog/ is the canonical list of what's changed — worth bookmarking. What downstream errors are you still hitting?

Arkadiusz Wroblewski

Hello @Denise Skidmore

Atlassian is fully phasing out app passwords in favor of API tokens, and the legacy merge parameter on diff/diffstat endpoints is being removed for topic=true/false. Hardcoded repository URLs are also no longer reliable compared to following direct API response links.

Check your workflow that nothing still relies on legacy authentication or manually built paths. Also, verify that your Code Insights annotations target the correct commit and report with the updated token scopes.

Cheers,

Arek🤠

Denise Skidmore

Change I saw was not listed. The Bitbucket Cloud REST API - diffstat is supposed to take two hashes and that now fails. The link in the PR information does work, it inserts the username before the hash.

My second error appears to be on my part, not sure how that particular case didn't come up before...

Denise Skidmore

OAuth clients is still working, I wasn't using app passwords. It was the REST API that changed.

Arkadiusz Wroblewski

Then that explains this.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

rest-api