Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bitbucket REST API - getting branches

Hi all,

Using the REST API we are trying to retrieve data about branches in the workspace. 

Using{workspace}/(repository}/refs/branches we get a response exampled in the link. It has values holding the various branches but does not hold any of the wanted data - author, created date etc. 

Unless it is the data specified under 'target' .. Is that the case (target references the requested branch), or are we using it wrong?

response example  


1 answer

1 accepted

0 votes
Answer accepted
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 23, 2022

G'day Tomer!

Welcome to the Bitbucket Cloud community! :) 

To retrieve information about certain ref types (ie branches/tags), you would need to modify the URL slightly by adding "/branches" or "/tags" after "ref", for example:{workspace}/(repository}/refs/branches{workspace}/(repository}/refs/tags

To filter this information further (for example - looking for a certain branch) the format is:

name ~ "insertnamehere"

Formatting this to unicode, you can include this in the url with the ?q parameter to view information about a certain branch:{workspace}/(repository}/refs/branches?q=name%7E%22{branchname}%22

Further information regarding querying/sorting can be found here:

Hope this helps.


- Ben (Bitbucket Cloud Support)

Hi Ben,

Thanks for your response. As detailed, we are using the URL as you provided -{workspace}/(repository}/refs/branches

  but we do not see the data we are looking for. Maybe asking this differently - what is the data provided under "target" in the response JSON?

We couldn't find what the target is referencing to.

Thanks again!

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 27, 2022

Hey Tomer,


Target refers to a few fields, "type", "hash" and "date", for example:

"type": "commit",
"hash": "b41a86ce2a7b1bd0c002743240a7cf93c09ce513",
"date": "2022-11-23T05:25:56+00:00",

This provides details about the branches, for example the latest commit hash and the date that the branch was last committed to.

What is the information you are hoping to return from the branches?

Hope this helps.


- Ben (Bitbucket Cloud Support)

Hi Ben,

For example who created the branch and when,amount of commit

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 28, 2022

Hey Tomer,

Unfortunately - the API will not show when the branch was created, only when the last commit was made.

There is a GIT command you can execute to show when each branch was created and by which author - although sometimes this is inaccurate:

git for-each-ref --format='%(committerdate)%09%(authorname)%09%(refname)' | sort -k5n -k2M -k3n -k4n | grep remotes | awk -F "\t" '{ printf "%-32s %-27s %s\n", $1, $2, $3 }'

As for total number of commits - this is also not reported by the API, however you can execute the following GIT command to count this on a per-branch basis:

git rev-list --all --count

Ultimately, the best way to find who created a branch is to check the first commit in the commit history. As reflogs are checked for author details using GIT commands such as above, these are set to expire in the GIT config (90 days by default) and this is what causes the inaccuracy.

Hope this helps.


- Ben (Bitbucket Cloud Support)

Like tomer bar likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events