No workspace with identifier '{xxx}'

[lijinbio]

Hi all,

My Bitbucket API stops working due to the following error.

```

$ curl -s -X GET -H 'Content-Type: application/json' "https://api.bitbucket.org/2.0/repositories/%7B$accountid%7D?access_token=$accesstoken"

{"type": "error", "error": {"message": "No workspace with identifier '{xxxxx}'."}}

```

In fact, this error has happened on Jan 17, 2020, but the bug occurs again. Please see below.

https://community.atlassian.com/t5/Bitbucket-questions/No-workspace-with-identifier-xxx/qaq-p/1274594

May I ask if we have an alternative API protocol? e.g., API 3.0? so that we can have a stable API connection to Bitbucket? Thank you.

Best regards,

Jin

[Patrick Wolf - Atlassian · Accepted solution]

Hi,

Firstly, for GDPR purposes we removed support for username in any API last year. We added a non-personal "workspace id" field for all accounts that could be used in place of username.

Secondly, we are in the middle of transitioning from User and Team accounts to Workspaces. With this change we are updating some APIs as well to reflect this change. 

We didn't intend for this to be a breaking change so we are temporarily updating the /repositories API endpoint to maintain support for the user's account_id. This fix should be available soon.

Support for accessing repository information via the user's account_id will end when we remove support for the /users and /teams API endpoints later this year. Going forward the best way to retrieve any repository information is to use the workspace_id or the UUID. The account_id is and will be the best way to identify a specific user.

Regards,  

Patrick

[lijinbio]

Hi Patrick,

Many thanks for your information. It works to use workspaces. Thanks.

Best regards,

Jin

[Anna]

Hi,

Please open a support ticket here and we can help you with this issue.

Thanks!

[lijinbio]

Hi Anna,

I just opened a ticket. See https://getsupport.atlassian.com/servicedesk/customer/portal/11/BBS-134515

Thank you.

Best regards,

Jin