Last week we published a deprecation notice to announce Atlassian is deprecating all Bitbucket Cloud’s v1 APIs to make way for more usable and maintainable alternatives in v2.
With that in mind, as of June 30, 2018 the Bitbucket Cloud v1 API is deprecated, and in accordance with the Atlassian REST API policy, all v1 APIs will be removed from Bitbucket Cloud’s API permanently on December 31, 2018.
What will happen if I do nothing?
When the v1 APIs are removed, any apps or services still using v1 resources will not work. If you currently rely on a script, integration, or app that makes requests using
/1.0/ resources, you should update it to use a
/2.0/ alternative as soon as possible.
The semantics of these v1 APIs were changed in a significant way, or will not be included in v2:
Changesets → Commits
Deploy keys → None
Events/Services → Webhooks
Followers → Watchers
Groups → None
Invitations → None
Links → Linkers
Privileges → Permissions
Oauth/Consumers → None
User → Read-only
Wiki → None
These are not all the v1 APIs that are deprecated, as such we strongly encourage you to read the full deprecation announcement for a comprehensive look at all the resources and methods affected, and for alternatives in Bitbucket Cloud’s v2 REST API.
Product Marketing Manager, Bitbucket Cloud