On April 30, 2021 Bitbucket /2.0/…/hooks API for retrieving webhooks will stop including the read-only hooks registered via Connect apps. If you are using these API endpoints, please see full details here.
Why is it changing?
There are limitations around the read-only portion of the hooks returned by these endpoints today. We believe the majority of use cases for /2.0/…/hooks API is related to hooks that users register themselves via Repository Settings or API, therefore would like to clean this up and let these endpoints focus on those hooks only.
What do I need to do?
If you are only using these API endpoints to retrieve the webhooks you registered via Repository Settings on Bitbucket Cloud UI or via webhooks API, then you do not need to do anything.
If you actually need to retrieve information on the webhooks registered by Connect apps, then please reply to this announcement with your use case, and we will work with you to find the best way forward.
Hi,
I need to retrieve information on the webhooks registered by Connect apps, my product relies on this. How can I obtain this info following your recent change in the API?
Thanks,
Roy
Per my comment on your support ticket, could you please provide us a bit more detail on your use case around these Connect apps read-only hooks, which exact fields you are using and what do you use them for?
Are you able to elaborate on why you need the list of 3rd party apps?
Using /2.0/hooks endpoint as it was previously would only give you the Connect apps that contained webhooks modules, which would not be a complete picture of all Connect apps installed into your workspace.
Hi Wendy,
I need this info as part of the visibility picture I create for my workspace. As an admin, I need to know which external apps (such as Snyk, SonarQube, etc.) have installed webhooks on the workspace repos. Until the recent change I managed to get this info via the /hooks REST API. Do you have an alternative way to gain this info that you can suggest?