How can I efficiently get the number of commits a branch is ahead/behind using the REST API?

[Adrian Price]

I'm trying to build reporting around branches' relative histories, so that we can:

• See what branches have been merged to the upstream branch and can be removed
• See what branches have commits that need to be merged to the upstream branch
• See what branches need to be merged from upstream in order to avoid conflicts when merging to upstream

Basically I want the same ahead/behind info that's shown in the Web UI's Branches page for a repo, but I need to automate reporting on it for multiple repositories at once.

Right now I have a working process via:

1. Get list of repos
2. For each repo, get list of branches
3. For each branch, get list of commits on that branch with ?exclude=<upstream> to see how many commits ahead it is
4. For each branch, get list of commits on the upstream branch with ?exclude=<branch> to see how many commits behind it is

This works, but rapidly hits the 1k/hr rate limit on calls to the commits route, and it's horribly slow with more than a handful of repos & branches, and worse yet with multiple pages of commits as the paginated commits API does not provide a full result set count. I understand the rate limits, and for the performance on both ends I would much rather a cleaner way of doing this, but I can't find any other option anywhere in the SDK docs. Have I missed something?

[Arthur Violy]

+1

Same question, same problem.

Why this feature available on Web UI is not available into API.

[Saif]

Absolutely a must feature.

We are highly interested in this. 

Any possible availability in near upcoming releases?

[Daniele Gaffuri]

Debugging front end I've found an internal API that is callable with OAuth: 

https://bitbucket.org/api/internal/repositories/<repo>/branch-list/?q=name != "master" AND (ahead = 0 OR ahead = null)

[elicier_molina_contractor]

One more here

[derbenoo]

+1

[manu]

+1 here.