Bitbucket Cloud API privacy updates | deprecation notice (12 Oct 2018)



You may have noticed that today (01 Oct 2018), we published API updates (related to privacy improvements) and migration guides for Confluence Cloud and Jira Cloud. The changes for Bitbucket Cloud will be similar (ex: use of the Atlassian user ID instead of usernames). A detailed migration guide for Bitbucket Cloud will follow later this month.



The Bitbucket API deprecation notice is now available.


TL;DR (but you really should read it):

  • Introducing two new fields to the object body, Atlassian account ID (account_id) and nickname.
  • Deprecating the use of usernames from user objects through the API.
  • Replacing username fields with Atlassian Account ID

Please take the time to read through the doc, and use this thread for questions.


Do the changes affect team objects?


Please find the new migration guide here!


It mostly focuses on User objects, but there is some changes to what team objects return about membership. Take a look at the guide for more information


There is a typo in the table for field links.html.href. It says ‘Returns the users avatar’.



In SonarCloud we want to display a link that will redirect user to its Bitbucket team or account (depending if our app was installed in a team or user account).
We were relying on links.html.href fields, that is planned for deletion. Can we still use it for teams? For users, is it fine to forge the URL:{user_uuid}?


I was also wondering how to provide a link to redirect to the Bitbucket team or account as asked by @julien.henry.

I was also wondering if the username field will still be returned with the team object as the team object doesn’t seem to return the nickname field.



thanks for pointing this out @julien.henry, will update accordingly.


Yes, you can forge the URL for now, but it will stop working in March, because we’re deprecating user profile pages (because GDPR means :zipper_mouth_face:).

We’re going to replace user profiles with a content-space for Users or Teams called a Workspace, which will serve as that new reference point, but it will only show what content is contained in that space.

So that is a long winded way of saying that the ability to point people at a user profile via the API is going away.


The team object will continue to return a username value, as Teams will still have unique names even in a future GDPR compliant world.


Thanks for the answers. I hope you will give us enough time between the introduction of Workspaces and the removal of{user_uuid} support so that we can update our app accordingly.