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

API request failed with status 401. Check your account and app password and try again.


Hi ,

I am unable to get the issue of pipe line trigger 

API request failed with status 401. Check your account and app password and try again.


I have verified already my USERNAME is only username and not email

I have verified the APP_PASSWORD is having repository permissions as well.

Any other suggestions to debug this issue


2 answers

2 accepted

2 votes
Answer accepted

Hello @M_kulshershtha ,

Welcome to Atlassian Community!

Receiving a 401 usually means your credentials are invalid or you lack permissions.

As you mentioned you are using an App Password already, could you please try creating a new app password with all the permissions checked and set its value in the variable BITBUCKET_APP_PASSWORD you are using in your build ? This is to check if the lack of permissions in your current app passwords is not the issue in this case.

Also, make sure you are using your bitbucket username, which you can find in your account's personal settings, as the $BITBUCKET_USERNAME variable in your pipeline.

Thank you, @M_kulshershtha .

Kind regards,

Patrik S

0 votes
Answer accepted

Thanks Pratik,

I am able to proceed now as I was not using correct password :)

Thanks for your pointers.



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events