Create a webhook for a workspace in Bitbucket
A documented Bitbucket operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Create a webhook for a workspace
- POSTChanges data · Workspaces
api.bitbucket.org/workspaces/{workspace}/hooks
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Bitbucket operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Bitbucket operations
- Add a new SSH keyPOST · changes data
- Create a snippetPOST · changes data
- Create a comment on a snippetPOST · changes data
- Create an issuePOST · changes data
- Create a comment on an issuePOST · changes data
- Create a snippet for a workspacePOST · changes data
- Delete an appDELETE · changes data
- Update an installed appPUT · changes data
Questions
- Can HumDay create a webhook for a workspace in Bitbucket?
- Yes. This operation is published in Bitbucket's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Bitbucket data?
- Yes — this is a POST operation, so it changes something in Bitbucket. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Bitbucket account.
Where this came from
Read from a published API description for Bitbucket at bitbucket.org/api/swagger.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.