Clarification needed for deprecated endpoints

[ploke]

Hi, there is some confusing information about the removal of certain endpoints from the V2 APIs.

In the migration guide, only `/2.0/users/{username}/members` is marked for deletion in June of this year, and doesn't make a mention of `/2.0/teams/{username}/members`

https://developer.atlassian.com/cloud/bitbucket/bbc-gdpr-api-migration-guide/

However, the following deprecation notice page shows both `/users/{username|uuid}/members` and `/teams/{username|uuid}/members` are slated for removal in June.

https://developer.atlassian.com/cloud/bitbucket/bitbucket-api-changes-gdpr/

So which one is accurate? I'd like to be able to query a team's members, at least by the team's UUID.

[jarredc · Accepted solution]

Hey Praneet, Thanks for pointing this out. 

The correct guide is https://developer.atlassian.com/cloud/bitbucket/bbc-gdpr-api-migration-guide/. Will update the other one to reflect the changes more accurately!

[ploke]

Hi, Jarred, that's great! Can you please confirm the following?

- The `/2.0/teams/{uuid}/members` endpoint is not subject to deprecation (and therefore, removal this April), with the caveat that the authenticated user must be an admin in order to list members of a Team.

- `username` will be removed from all responses, including those of Teams, with the exception of the response for the `/user` endpoint, which returns only the currently authenticated user.

Also, I don't see any endpoints for listing user groups. Is that intentional?

[jarredc]

Hey Praneet, 

That's right. 2.0/teams/uuid/members will not be deprecated. 

re: Groups, Yes. User management should be done through some kind of SCIM / SAML solution.

Jarred

[ploke]

Ping @jarredc