Bitbucket logo

Bitbucket

Dev ToolsBasic authLive

Your customers connect their Bitbucket Cloud workspace once and Askel takes it from there. Pull requests, pipeline runs, repository events, and commit metadata flow into your product without your team writing a single line of webhook plumbing. Askel handles Basic auth, token storage, and header composition so your codebase stays clean.

What you can do

React to pull request lifecycle events

Trigger workflows when a PR is opened, marked as ready, approved, declined, or merged. Filter by target branch, reviewer, or repository so only the events your product needs actually land in your ingest endpoint.

Track Bitbucket Pipelines run results

Subscribe to pipeline step completions and surface pass or fail status in your product alongside the commit SHA and branch that triggered the build. Useful for release gates and deployment dashboards.

Read and write issues

Pull open issues from any authorized repository, update their status, assign them, or add comments. Mark issues as resolved once your product has processed them to keep the two systems in sync.

Fetch commit and branch metadata

Read branch names, latest commit SHAs, and commit messages for the repositories in scope. Lets your product link its own records to the exact commit that produced them.

Register and manage webhooks without leaving your product

Askel registers the Bitbucket webhook on the customer's workspace at connect time and removes it on disconnect. Your team never has to ask a customer to set up a webhook manually.

Scope access to specific repositories

Customers can authorize a single repo, a handful of repos, or the entire workspace. Askel enforces that boundary and will not request data from repositories outside the agreed scope.

Sample use case

Blocking a release until every PR on a target branch is merged

You sell release-management software. A customer, Harborview Labs, runs three microservices in a workspace called harborview. Their release process requires that every open pull request targeting the release/2.5 branch be merged or declined before the weekly deployment window opens. Today that check is a manual Slack message and a spreadsheet.

  1. 1

    Connect Bitbucket

    Harborview's admin clicks Connect Bitbucket inside your product. They paste their Atlassian email and an API token scoped to the harborview workspace. Askel composes the Basic auth header and verifies the credentials against https://api.bitbucket.org/2.0/user before storing them.

  2. 2

    Configure the watch rule

    In your product's onboarding wizard, a Harborview admin sets the workspace to harborview, the repository to harborview/platform, and the target branch filter to release/2.5. Askel registers the pullrequest webhook on the repo automatically.

  3. 3

    Events start flowing

    Each time a PR targeting release/2.5 is opened, updated, approved, or merged, Askel forwards a structured event to your product's ingest endpoint with the PR title, author, reviewers, approval count, and current state.

  4. 4

    Your product builds the blocking list

    Your product queries the current open PRs for release/2.5, finds the two PRs that are still awaiting approval, and surfaces them in the release dashboard with direct Bitbucket links and reviewer names.

  5. 5

    Release gate clears automatically

    Once the last open PR is merged, Askel sends the pullrequest:fulfilled event, your product marks the release/2.5 gate as green, and the release lead gets a notification that the deployment window can open.

Authentication

Basic auth

Customer's Bitbucket admin generates a scoped API token at id.atlassian.com/manage-profile/security/api-tokens and pastes it into Askel along with the admin's Atlassian email. Askel composes the Basic auth header at request time; the token never reaches your servers.

Data flow

How Askel sits between your product and the customer's system

Data flow between Customer's Bitbucket workspace, Askel, and Your productCustomer's Bitbucket workspaceAPI endpointAskelauth · mapping · driftYour productyour backend
RepositoriesPull requestsIssuesPipelinesWebhooksCommits

FAQ for Bitbucket

Does this work with Bitbucket Server or Data Center, or only Bitbucket Cloud?+
Today Askel connects to Bitbucket Cloud at api.bitbucket.org/2.0. Bitbucket Server and Data Center use a different REST API and a different auth model. If your customers are on Server or Data Center, let us know and we can scope out a separate connector.
What scope does the API token need?+
The Atlassian API token inherits the permissions of the account that generated it. We recommend the customer create a dedicated service account with read access to the target repositories and write access only where your product needs to push back (comments, issue status). Using a personal admin account works but carries broader permissions than necessary.
What happens if the customer rotates their API token?+
Askel will start receiving 401 responses and marks the connection as degraded within minutes. Your product surfaces a reconnect prompt to the customer so they can paste the new token. No data is lost during the gap; Askel replays any missed webhook events once the connection is restored.
Can a customer connect multiple Bitbucket workspaces?+
Yes. Each workspace is a separate Askel connection with its own credentials and webhook registrations. Your product receives events tagged with the connection ID so you can route them to the right customer context.
Ready to ship integrations faster?customers faster?implementations faster?
Join onboarding teams delivering integrations without the engineering queue,
catching drift before it breaks, and hitting go-live dates.
Security & Compliance
ISO 27001 Certified
GDPR Compliant

© 2025 Askel.ai. All rights reserved.