How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bitbucket Pipelines Commits API

These are the repository's commits. They are paginated and returned inreverse chronological order, similar to the output of git log.

Bitbucket Pipelines Commits API is one of 23 APIs that Bitbucket Pipelines publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Commits. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 25 operations across 14 paths, and defines 28 schemas. It is described by OpenAPI 2.0, at version 2.0.

Requests are made against the base URL https://api.bitbucket.org/2.0.

25 operations 14 paths 28 schemas 4 DELETE13 GET5 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
2.0
Base URL
https://api.bitbucket.org/2.0
Authentication
basic, OAuth 2.0, API Key
Terms of Service
Resource Areas
1

Authentication & Security 3

Bitbucket Pipelines Commits API declares 3 security schemes for authenticating requests. It defines a basic scheme (basic). It supports OAuth 2.0 (oauth2) using the accessCode flow, exposing 26 scopes. An API key is passed in the header as Authorization (api_key).

  • basic — Basic HTTP Authentication as per [RFC-2617](https://tools.ietf.org/html/rfc2617) (Digest not supported). Note that Basic Auth is available only with username a…
  • oauth2 — OAuth 2 as per [RFC-6749](https://tools.ietf.org/html/rfc6749).
  • api_key — API Keys can be used as Basic HTTP Authentication credentials and provide a substitute for the account's actual username and password. API Keys are only availa…

Paths & Operations 25

Across 14 paths, the API surfaces 25 operations — 4 DELETE, 13 GET, 5 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Commits 25

These are the repository's commits. They are paginated and returned in reverse chronological order, similar to the output of git log.

GET
/repositories/{workspace}/{repo_slug}/commit/{commit}
Get a commit
3 params → 200404
DELETE
/repositories/{workspace}/{repo_slug}/commit/{commit}/approve
Unapprove a commit
3 params → 204404
POST
/repositories/{workspace}/{repo_slug}/commit/{commit}/approve
Approve a commit
3 params → 200404
GET
/repositories/{workspace}/{repo_slug}/commit/{commit}/comments
List a commit's comments
5 params → 200
POST
/repositories/{workspace}/{repo_slug}/commit/{commit}/comments
Create comment for a commit
4 params → 201400404
DELETE
/repositories/{workspace}/{repo_slug}/commit/{commit}/comments/{comment_id}
Delete a commit comment
4 params → 204404
GET
/repositories/{workspace}/{repo_slug}/commit/{commit}/comments/{comment_id}
Get a commit comment
4 params → 200
PUT
/repositories/{workspace}/{repo_slug}/commit/{commit}/comments/{comment_id}
Update a commit comment
5 params → 201400
GET
/repositories/{workspace}/{repo_slug}/commit/{commit}/reports
List reports
getReportsForCommit 3 params → 200
PUT
/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}
Create or update a report
createOrUpdateReport 5 params → 200400
GET
/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}
Get a report
getReport 4 params → 200404
DELETE
/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}
Delete a report
deleteReport 4 params → 204
GET
/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations
List annotations
getAnnotationsForReport 4 params → 200
POST
/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations
Bulk create or update annotations
bulkCreateOrUpdateAnnotations 5 params → 200
GET
/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations/{annotationId}
Get an annotation
getAnnotation 5 params → 200404
PUT
/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations/{annotationId}
Create or update an annotation
createOrUpdateAnnotation 6 params → 200400
DELETE
/repositories/{workspace}/{repo_slug}/commit/{commit}/reports/{reportId}/annotations/{annotationId}
Delete an annotation
deleteAnnotation 5 params → 204
GET
/repositories/{workspace}/{repo_slug}/commits
List commits
2 params → 200404
POST
/repositories/{workspace}/{repo_slug}/commits
List commits with include/exclude
2 params → 200404
GET
/repositories/{workspace}/{repo_slug}/commits/{revision}
List commits for revision
3 params → 200404
POST
/repositories/{workspace}/{repo_slug}/commits/{revision}
List commits for revision using include/exclude
3 params → 200404
GET
/repositories/{workspace}/{repo_slug}/diff/{spec}
Compare two commits
10 params → 200555
GET
/repositories/{workspace}/{repo_slug}/diffstat/{spec}
Compare two commit diff stats
8 params → 200555
GET
/repositories/{workspace}/{repo_slug}/merge-base/{revspec}
Get the common ancestor between two commits
3 params → 200401403404
GET
/repositories/{workspace}/{repo_slug}/patch/{spec}
Get a patch for two commits
3 params → 200555

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are paginated_changeset (6 properties), diffstat (6 properties), paginated_reports (6 properties), paginated_diffstats (6 properties). Each schema is shown below with its type and property counts.

project
report
base_commit
object
object
Base type for most resource objects. It defines the common type element that identifies an object's type. It also identifies the element as Swagger's discrimin…
1 property 1 required
paginated_reports
object
A paginated list of reports.
6 properties
paginated_diffstats
object
A paginated list of diffstats.
6 properties
commit_file
object
A file object, representing a file at a commit in a repository
5 properties 1 required
report_annotation
account
branch
participant
comment
team_links
commit_comment
ref
object
A ref object, representing a branch or tag in a repository.
4 properties 1 required
report_data
object
A key-value element that will be displayed along with the report.
3 properties
author
error
object
Base type for most resource objects. It defines the common type element that identifies an object's type. It also identifies the element as Swagger's discrimin…
2 properties 1 required
committer
paginated_annotations
object
A paginated list of annotations.
6 properties
paginated_commit_comments
object
A paginated list of commit comments.
6 properties
account_links
object
Links related to an Account.
1 property
commit
repository
link
object
A link to a resource related to this object.
2 properties
team
diffstat
object
A diffstat object that includes a summary of changes made to a file between two commits.
6 properties 1 required
paginated_changeset
object
A paginated list of commits.
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bitbucket-pipelines-commits-api-openapi.yml Raw ↑

Other APIs Bitbucket Pipelines publishes across the network.

Bitbucket Pipelines Addon API
Bitbucket Pipelines Branch restrictions API
Bitbucket Pipelines Branching model API
Bitbucket Pipelines Commit statuses API
Bitbucket Pipelines Deployments API
Bitbucket Pipelines Downloads API
Bitbucket Pipelines GPG API
Bitbucket Pipelines Issue tracker API
Bitbucket Pipelines Pipelines API
Bitbucket Pipelines Projects API
Bitbucket Pipelines properties API
Bitbucket Pipelines Pullrequests API
Where this information came from

This is an independent, third-party profile of Bitbucket Pipelines Commits API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.