← All integrations

Bitbucket

104 operations0 webhooks

Git repository hosting for source code, pull requests, and CI/CD pipelines.

Supported operations

  • Create Repositories Commit Reports AnnotationsWrite

    Adds multiple annotations to a commit report in bulk. Use when you need to add code analysis findings (vulnerabilities, code smells, bugs) to a report attached to a specific commit.

  • Create Repositories Commits2Write

    Tool to list commits from a revision using POST method. Identical to GET endpoint but allows sending include/exclude parameters in request body to avoid URL length limits. Use when include/exclude parameters are too long for query strings.

  • Delete Commit CommentDestructive

    Permanently deletes a specific comment on a commit. Use when removing outdated, incorrect, or unwanted feedback on a commit.

  • Delete Repositories Commit Reports AnnotationsDestructive

    Deletes a single annotation matching the provided ID from a commit report. Use when you need to remove a specific annotation from a code analysis report.

  • Get Commit Build StatusRead-only

    Get a specific build status for a commit in Bitbucket. Use when you need to check the status of a particular build/CI run for a commit.

  • Get Commit ChangesRead-only

    Tool to retrieve a page of changes made in a specified commit, showing all changed files with their change statistics (lines added/removed, status). Use when you need to enumerate files modified in a specific commit or commit range.

  • Get Commit CommentRead-only

    Retrieves a specific comment from a commit by its ID. Use when you need to fetch details of a particular commit comment including content, author, timestamps, and inline location.

  • Get Commit DiffRead-only

    Tool to retrieve the unified diff between two provided revisions or for a single commit in a Bitbucket repository. Use when you need to see the actual code changes in a commit or between two commits. Supports filtering by file path and various diff options.

  • Get Repositories CommitRead-only

    Tool to retrieve detailed information about a specific commit in a Bitbucket repository. Use when you need to get complete commit details including author, message, date, parents, and related links.

  • Get Repositories Commit CommentsRead-only

    Retrieves all comments on a specific commit in a Bitbucket repository. Returns both global and inline code comments. Use when you need to view feedback, discussions, or notes left on a specific commit.

  • Get Repositories Commit ReportRead-only

    Returns a single report matching the provided ID from a commit. Use when you need to retrieve details of a specific analysis report (e.g., security scan, code coverage, test results, or bug report) for a commit.

  • Get Repositories Commit ReportsRead-only

    Tool to get reports linked to a specific commit. Use when you need to retrieve analysis results, test reports, security scans, or code coverage data associated with a commit.

  • Get Repositories Commit Reports AnnotationsRead-only

    Returns a single annotation matching the provided ID from a commit report. Use when you need to retrieve details of a specific code analysis finding (e.g., vulnerability, code smell, or bug) identified in a commit.

  • Get Repositories Commit StatusesRead-only

    Returns all build statuses (e.g., CI/CD pipeline results) for a specific commit. Use when you need to check build status, verify test results, or monitor deployment pipelines for a particular commit.

  • Get Repositories Merge BaseRead-only

    Get the merge base (best common ancestor) between two commits in a Bitbucket repository. Use when you need to find the common ancestor commit between two branches or commits for comparison or merge operations.

  • Get Repository PatchRead-only

    Tool to retrieve the git patch content for a Bitbucket repository at a specified revision or commit range. Use when you need to review code changes, generate diffs, or analyze modifications between commits. Returns raw patch in unified diff format.

  • List CommitsRead-only

    Tool to retrieve a page of commits from a Bitbucket repository. Returns commits in reverse chronological order (newest first), similar to git log. Use when you need to browse commit history, filter commits by branch/tag, or restrict to commits affecting a specific path.

  • List Commits From RevisionRead-only

    Tool to list commits starting from a specific revision in a Bitbucket repository. Commits are paginated and returned in reverse chronological order. Use when you need to retrieve commit history from a specific commit, branch, or tag.

  • List Commits On MasterRead-only

    Lists commits on the master branch of a Bitbucket repository. Use when you need to retrieve the commit history for the master branch, including commit messages, authors, dates, and parent relationships.

  • Update Insights Projects Repos Commits ReportsWrite

    Create or update an insight report for a commit. Creates a new report if it doesn't exist, or replaces the existing one if a report already exists for the given repository, commit, and report key. Note: replacing an existing report will be rejected if the authenticated user was not the creator of the specified report.

  • Update Repositories Commit CommentsWrite

    Updates the contents of a comment on a commit. Use when you need to modify an existing comment's text on a commit.

  • Update Repositories Commit Reports AnnotationsWrite

    Creates or updates an individual annotation for a commit report. Use when you need to add or modify code analysis findings (vulnerabilities, code smells, or bugs) identified in a commit.

FAQ

Install corsair and @corsair-dev/bitbucket, add the Bitbucket plugin, and connect with OAuth. Then call methods like corsair.bitbucket.api.commitsAndInsights.createRepositoriesCommitReportsAnnotations() from your app. Corsair stores tokens, and syncs data per tenant.

Yes. Bitbucket needs an OAuth app with scopes that match what you automate. Register the app in Bitbucket, configure redirect URLs, then connect through Corsair or managed OAuth in Hub.

Yes. One Corsair client can hit Bitbucket, GitHub, Notion, Stripe, and the rest. Trigger Bitbucket from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for git repository hosting for source code, pull requests, and ci/cd pipelines. Common builds include sync jobs, admin tooling, and agents that call Bitbucket APIs from your backend. Local DB entities let you query synced Bitbucket records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Bitbucket API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/bitbucket in the open repo. When Bitbucket ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Bitbucket data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Bitbucket data on your behalf.