Bitbucket 2.0 API diff across private forks

[Tyler Mann]

Is it possible to use the diff API across a private fork?

For example, if I have a private repository named: `repo/test` and I create a private fork of it `forked/test`. And and then I create a pull request from `forked/test` with a target of master on the original `repo/test`. I can see the pull request and changes in the bitbucket cloud UI, I can also use a url like this to compare the diff across the forked repository: https://bitbucket.org/repo/test/branches/compare/forked/test:f3609a3ec1e7..a36c91c1cf88#diff

However if I try to call the diff api with something like this with an auth token for repo/test I just get a 404: https://api.bitbucket.org/2.0/repositories/repo/test/diff/forked/test:f3609a3ec1e7..a36c91c1cf99

Is there a way to get similar results to what the internal APIs are using? Because these pull requests are listed from the repo/test user's token so I would assume it would have the same behavior as the UI.

[Daniil Penkin]

Hello @Tyler Mann,

The diff API URL you mentioned looks good to me, just tried it out with a pair of private repository and its fork in my account.

Is any particular error returned along with 404? Maybe the token you're using for REST API call doesn't have access to both repositories?

Cheers,
Daniil

[Tyler Mann]

Hi @Daniil Penkin thanks for the quick response and helping test this out on your side. The message in the 404 is like this: "a36c91c1cf88..fork/test:f3609a3ec1e7"

Digging into this a little more and adding more context: we are using a bitbucket connect app access token for our authentication that is installed to the repo/test account and can request normal diffs within that account just fine.

This access token I am testing with does not have read access to the other fork/test repository, although it does list the forked pull request in the repo/test pull requests and its commits from the API. And any user of the repo/test repository can see the contents of the diff from this pull request on fork/test within the bitbucket UI even if it doesn't have access to the fork/test repo. I tried this out with another user account forking the repo into a private repo that my main account doesn't have access to and it still shows the diff in the UI for the pull request. However I can't request it via the API without a 404.

So I guess my theory is that it seems like maybe the security model applied to at least bitbucket connect apps is inconsistent with a user in the UI.

Thanks again for any help here! Trying to help support some of our customers that are using this flow.

[Martyn Lloyd-Kelly]

What was the resolution of this? I'm attempting to do the exact same and getting a 404 too. However, I have the required privileges on my user account!

[Tyler Mann]

@Martyn Lloyd-Kelly We weren't able to reach a resolution here yet unfortunately. We were able to get things working for github, gitlab, and bitbucket server using a different method of accessing remote refs for the pull requests in the git repo itself. However still not sure if its possible with bitbucket cloud as those remote refs don't exist that we could tell and we were getting these 404's from the APIs.

[Martyn Lloyd-Kelly]

@Tyler Mann That's a shame, sorry to hear you couldn't get it working :-( I did manage to get something other than a 404 by sending the following:

https://api.bitbucket.org/2.0/repositories/team_slug/source_repo_slug/diff/team_slug/destination_repo_slug:HEAD..HEAD

However, I don't think the endpoint is going to provide us with what we need to address the issue here since its just comparing two individual commits, not the whole difference between the two HEAD commits. I'm instead going to try and create a pull request using the API, then extract the files to be changed from the PR (again using the API), and go from there. Not sure if that strategy may help you too?

```Thanks for responding to me though, its very much appreciated!