JIRA Rest API authentication always returns 401 unauthorized

I have been trying for hours the following simple CURL command described in the documentation without any success. It always returns me a 401 unauthorized.

curl -D- -u "email:password" -X GET -H "Content-Type: application/json" https://textmaster.jira.com/rest/api/2/issue/TM-3450

I have checked that my confluence config has the "allow remote api calls" set to true. What should I do to make this work?


Note: I'm able to access the rest API from the browser directly, while logged in with my user account.

Note: It's a linked google account with a password set.

3 answers

1 accepted

Accepted Answer
10 votes

Hi Pierre-Louis,

Silly question but your email is your username? if not then your command should be replaced with JIRA username. Also since your connection is https but -k at the end of the URL  and try again

curl -D- -u "username:password" -X GET -H "Content-Type: application/json" https://textmaster.jira.com/rest/api/2/issue/TM-3450 -k 

Also if that is not the case then you can try other authentication technique like Oauth.


I just wanted to add a comment because I skipped by this answer and then kept looking for a while before realizing this was the correct answer. Even though I login to confluence with `nate@mydomain.com`, that is not the username to user when authenticating against the api. Against the api, I have to use `nate` as the username.

This can't be stated enough. The API docs aren't clear and make it sound like the website authentication is exactly the same as the rest API authentication. The website works with both username and email as the "username" while the rest API only works with username. You can see your "username" by viewing your profile in JIRA.

Jesus... I spent hours trying to figure out why, are we supposed to be mind readers? You have to emphasize this fact in your documentation, since it's almost ubiquitous that both email and username can be used to authenticate.

Thank goodness; yes this solved it.

To complicate matters, the REST API was accepting with the email address as the login ID for the first minute or so after the first login with a new account, so it was working for a while ... and then not.

@ Jonathan Sullivan

My username is also my email address but Jira won't allow me to change the username to a new username.  So what can I do to make my authentication API work?

  Let say my email address is "nguyen7744@yahoo.com", can I send my authentication as: 

curl -D- -u "nguyen7744:password1234" -X GET -H "Content-Type: application/json" https://textmaster.jira.com/rest/api/2/issue/TM-3450


If that won't work then how can I change my current username (nguyen7744@yahoo.com) to a new username? Or I need to contact JIra's support?


John Nguyen

Note that if you are logging in via a sync Google account, it is NOT the google password you are supposed to use. Also it is not the email.

Instead you should go to your user profile and look up your username and set a password.


For site admin functions, RSS feeds, REST API access, or WebDAV uploads you'll need to have an Atlassian Cloud password (separate to your Google Apps password. If you haven't set an Atlassian Cloud password, go to the login page and choose Unable to access your account? in the Atlassian Cloud login section.

Of course it makes no sense that this information is not available on the REST API documentation page, since it is quite crucial to get it working.

Is there a way to do this in the new JIRA experience? I can't seem to find any information and the link you provided is now dead.

Having the same issue.

Faced the same issue and found the solution (as of June 2018).

The username IS the full email.

The password is NOT your password to login, but an API token. To generate an API token, go to https://id.atlassian.com/manage/api-tokens# and create a new one.


So the username is the full email and the password is the API token from above step for using basic auth with Jira API.

Thanks it works for me

I am still facing the issue. This is what I have configured in Jenkins (Jira Issue Updater 1.18):


Username: {Email} (also set as the username)

Password: {Token}

Am I missing any step? Appreciate your response.


Thanks for the tip!

@Jesper den Boer - I am still not able to get it to work with the configuration posted above. Did you do anything different?

Use your Google email as the username and the generated API token as the password.

Thanks, this helped.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

26,413 views 2 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you