This page shows you how to allow REST clients to authenticate themselves using basic authentication with an Atlassian account email address and API token. This is one of three methods that you can use for authentication against the Jira REST API; the other two are cookie-based authentication and OAuth.
Have you picked the right authentication method?
Jira's REST API is protected by the same restrictions which are provided via Jira's standard web interface. This means that if you do not log in, you are accessing Jira anonymously. Furthermore, if you log in and do not have permission to view something in Jira, you will not be able to view it using the Jira REST API either.
In most cases, the first step in using the Jira REST API is to authenticate a user account with your Jira site. On this page we will show you a simple example of basic authentication.
API tokens are the the recommended method for using basic auth. You can generate an API token for your Atlassian account and use it to authenticate anywhere where you would have used a password. This enhances security because you are not saving your primary account password outside of where you authenticate, you can quickly revoke individual API tokens on a per-use basis, and API tokens will allow you to authenticate even if your Atlassian Cloud organization has two-factor authentication or SAML enabled.
Follow the instructions here to generate an API token.
Most client software provides a simple mechanism for supplying a user name (in our case, the email address) and password (or API token) that it then uses to build the required authentication headers automatically. For example, you can specify the argument with cURL as follows:
1 2 3 4 5
curl -D- \ -u email@example.com:freds_api_token \ -X GET \ -H "Content-Type: application/json" \ https://your-domain.atlassian.net/rest/api/2/issue/createmeta
If you need to, you may construct and send basic auth headers yourself. To do this you need to perform the following steps:
1 2 3 4 5
curl -D- \ -X GET \ -H "Authorization: Basic ZnJlZDpmcmVk" \ -H "Content-Type: application/json" \ "https://your-domain.atlassian.net/rest/api/2/issue/QA-31"
Because Jira permits a default level of access to anonymous users, it does not supply a typical authentication challenge. Some HTTP client software expect to receive an authentication challenge before they will send an authorization header. This means that it may not behave as expected. In this case, you may need to configure it to supply the authorization header, as described above, rather than relying on its default mechanism.
A CAPTCHA is 'triggered' after several consecutive failed log in attempts, after which the user is required to interpret a distorted picture of a word and type that word into a text field with each subsequent log in attempt. If CAPTCHA has been triggered, you cannot use Jira's REST API to authenticate with the Jira site.
You can check this in the error response from Jira -- If there is an header with a a value of , this means the application rejected the login without even checking the password. This is the most common indication that Jira's CAPTCHA feature has been triggered.