Hi @Miao Miao Li ,
When you create an app password, you select specific permissions for it. One possibility is that the app password does not have enough permissions for the endpoint you are using. E.g. if you're trying to read pull requests via API and the app password does not have permissions to read pull requests, then the request will fail.
Since it is not possible to view the permissions of an existing app password, I would suggest creating a new one, double check that it has appropriate permissions for the API endpoint(s) you want to use, and then make a new call with the new app password and see if it works.
If you're still having issues, please let me know:
1. the exact API call you are making
(please feel free to replace the actual workspace-id and the repo name in the URL when you paste it here, with something like <workspace-id> and <repo-name>)
2. what is the exact response you are receiving when you make the call
so I can better help you.
Hi @Miao Miao Li ,
For API calls the Bitbucket username should be used, instead of the email. The email is only used for logging in to Bitbucket website. For operations like cloning/pulling/pushing via HTTPS and also for API calls, the username should be used instead.
You mentioned that you solved this by removing the request body, I'm glad you managed to figure this out.
I am not sure though what request body you were using? An API call to retrieve a workspace's repos doesn't require you to send additional data with a request body.
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events