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 Issue tracker API

The issue resources provide functionality for getting information onissues in an issue tracker, creating new issues, updating them and deletingthem.You can access public issues without authentication, but you can't gain accessto private repositories' issues. By authenticating, you will get the abilityto create issues, as well as access to updating data or deleting issues youhave access to. Issue Tracker features are not supported for repositories in workspaces administered through admin.atlassian.com.

Bitbucket Issue tracker API is one of 23 APIs that Bitbucket publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 8 JSON Schema definitions.

Tagged areas include Issue tracker. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, an AsyncAPI specification, and 8 JSON Schemas.

This API exposes 33 operations across 19 paths, and defines 33 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.

33 operations 19 paths 33 schemas 5 DELETE18 GET6 POST4 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 Issue tracker 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 33

Across 19 paths, the API surfaces 33 operations — 5 DELETE, 18 GET, 6 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Issue tracker 33

The issue resources provide functionality for getting information on issues in an issue tracker, creating new issues, updating them and deleting them. You can access public issues…

GET
/repositories/{workspace}/{repo_slug}/componentsdeprecated
List components
2 params → 200404
GET
/repositories/{workspace}/{repo_slug}/components/{component_id}deprecated
Get a component for issues
3 params → 200404
GET
/repositories/{workspace}/{repo_slug}/issuesdeprecated
List issues
2 params → 200404
POST
/repositories/{workspace}/{repo_slug}/issuesdeprecated
Create an issue
3 params → 201401403404
POST
/repositories/{workspace}/{repo_slug}/issues/exportdeprecated
Export issues
3 params → 202401403404
GET
/repositories/{workspace}/{repo_slug}/issues/export/{repo_name}-issues-{task_id}.zipdeprecated
Check issue export status
4 params → 202401403404
GET
/repositories/{workspace}/{repo_slug}/issues/importdeprecated
Check issue import status
2 params → 200202401403404
POST
/repositories/{workspace}/{repo_slug}/issues/importdeprecated
Import issues
2 params → 202401403404409
DELETE
/repositories/{workspace}/{repo_slug}/issues/{issue_id}deprecated
Delete an issue
3 params → 204403404
GET
/repositories/{workspace}/{repo_slug}/issues/{issue_id}deprecated
Get an issue
3 params → 200403404410
PUT
/repositories/{workspace}/{repo_slug}/issues/{issue_id}deprecated
Update an issue
3 params → 200403404
GET
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/attachmentsdeprecated
List attachments for an issue
3 params → 200401404
POST
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/attachmentsdeprecated
Upload an attachment to an issue
3 params → 201400401404
DELETE
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/attachments/{path}deprecated
Delete an attachment for an issue
4 params → 204401404
GET
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/attachments/{path}deprecated
Get attachment for an issue
4 params → 302401404
GET
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/changesdeprecated
List changes on an issue
5 params → 200404
POST
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/changesdeprecated
Modify the state of an issue
4 params → 201401403404
GET
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/changes/{change_id}deprecated
Get issue change object
4 params → 200404
GET
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/commentsdeprecated
List comments on an issue
4 params → 200
POST
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/commentsdeprecated
Create a comment on an issue
4 params → 201400
DELETE
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments/{comment_id}deprecated
Delete a comment on an issue
4 params → 204
GET
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments/{comment_id}deprecated
Get a comment on an issue
4 params → 200
PUT
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments/{comment_id}deprecated
Update a comment on an issue
5 params → 200400
DELETE
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/votedeprecated
Remove vote for an issue
3 params → default
GET
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/votedeprecated
Check if current user voted for an issue
3 params → 204401404
PUT
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/votedeprecated
Vote for an issue
3 params → 204401404
DELETE
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/watchdeprecated
Stop watching an issue
3 params → 204401404
GET
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/watchdeprecated
Check if current user is watching a issue
3 params → 204401404
PUT
/repositories/{workspace}/{repo_slug}/issues/{issue_id}/watchdeprecated
Watch an issue
3 params → 204401404
GET
/repositories/{workspace}/{repo_slug}/milestonesdeprecated
List milestones
2 params → 200404
GET
/repositories/{workspace}/{repo_slug}/milestones/{milestone_id}deprecated
Get a milestone
3 params → 200404
GET
/repositories/{workspace}/{repo_slug}/versionsdeprecated
List defined versions for issues
2 params → 200404
GET
/repositories/{workspace}/{repo_slug}/versions/{version_id}deprecated
Get a defined version for issues
3 params → 200404

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are issue_change (8 properties), paginated_components (6 properties), paginated_milestones (6 properties), issue_job_status (6 properties). Each schema is shown below with its type and property counts.

base_commit
version
repository
paginated_milestones
object
A paginated list of issue tracker milestones.
6 properties
issue
issue_change
object
An issue change.
8 properties 1 required
paginated_log_entries
object
A paginated list of issue changes.
6 properties
committer
author
paginated_issues
object
A paginated list of issues.
6 properties
milestone
paginated_issue_comments
object
A paginated list of issue comments.
6 properties
ref
object
A ref object, representing a branch or tag in a repository.
4 properties 1 required
export_options
object
Options for issue export.
5 properties 1 required
issue_job_status
object
The status of an import or export job
6 properties
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
commit
link
object
A link to a resource related to this object.
2 properties
paginated_components
object
A paginated list of issue tracker components.
6 properties
paginated_versions
object
A paginated list of issue tracker versions.
6 properties
comment
issue_comment
component
account
participant
account_links
object
Links related to an Account.
1 property
paginated_issue_attachments
object
A paginated list of issue attachments.
6 properties
branch
team_links
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
team
project
issue_attachment

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bitbucket-issue-tracker-api-openapi.yml Raw ↑

Other APIs Bitbucket publishes across the network.

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

This is an independent, third-party profile of Bitbucket Issue tracker 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.