---
title: "List commit statuses for a commit"
method: GET
path: "/repositories/{workspace}/{repo_slug}/commit/{commit}/statuses"
tags: ["Commit statuses"]
---

# List commit statuses for a commit

`GET /repositories/{workspace}/{repo_slug}/commit/{commit}/statuses`

Returns all statuses (e.g. build results) for a specific commit.

## Query parameters

- `refname` string
- `q` string
- `sort` string

## Response `200`

A paginated list of all commit statuses for this commit.

- PaginatedCommitstatuses — A paginated list of commit status objects.
  - `size` integer — Total number of objects in the response. This is an optional element that is not provided in all responses, as it can be expensive to compute.
  - `page` integer — Page number of the current results. This is an optional element that is not provided in all responses.
  - `pagelen` integer — Current number of objects on the existing page. The default value is 10 with 100 being the maximum allowed value. Individual APIs may enforce different values.
  - `next` string, uri — Link to the next page if it exists. The last page of a collection does not have this value. Use this link to navigate the result set and refrain from constructing your own URLs.
  - `previous` string, uri — Link to previous page if it exists. A collections first page does not have this value. This is an optional element that is not provided in all responses. Some result sets strictly support forward navigation and never provide previous links. Clients must anticipate that backwards navigation is not always available. Use this link to navigate the result set and refrain from constructing your own URLs.
  - `values` Commitstatus[]
    - `type` string, required
    - `links` object
      - `self` object — A link to a resource related to this object.
        - `href` string, uri
        - `name` string
      - `commit` object — A link to a resource related to this object.
        - `href` string, uri
        - `name` string
    - `key` string, required — An identifier for the status that's unique to its type (current "build" is the only supported type) and the vendor, e.g. BB-DEPLOY
    - `refname` string — The name of the ref that pointed to this commit at the time the status object was created. Note that this the ref may since have moved off of the commit. This optional field can be useful for build systems whose build triggers and configuration are branch-dependent (e.g. a Pipeline build). It is legitimate for this field to not be set, or even apply (e.g. a static linting job).
    - `url` string — A URL linking back to the vendor or build system, for providing more information about whatever process produced this status. Accepts context variables `repository` and `commit` that Bitbucket will evaluate at runtime whenever at runtime. For example, one could use https://foo.com/builds/{repository.full_name} which Bitbucket will turn into https://foo.com/builds/foo/bar at render time.
    - `state` 'FAILED' | 'INPROGRESS' | 'STOPPED' | 'SUCCESSFUL', required — Provides some indication of the status of this commit
    - `name` string — An identifier for the build itself, e.g. BB-DEPLOY-1
    - `description` string — A description of the build (e.g. "Unit tests in Bamboo")
    - `created_on` string, date-time
    - `updated_on` string, date-time

## Other responses

- `401` — If the repository is private and the request was not authenticated.
- `404` — If the repository or commit does not exist

---

[API](https://skmtc.dev/bitbucket/apis/bitbucket-api.md) · [All operations](https://skmtc.dev/bitbucket/apis/bitbucket-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/bitbucket/bitbucket-api/revisions/952ded611d03/schema)