Jira

API configuration: jira, jira-basic

​

Features

​

Getting started

• Registering an App
• OAuth-related docs
• List of OAuth scopes
• API v3 docs
• OAuth app list (developer console)
• API rate limits
• Basic Auth-related docs

​

API gotchas

• Refreshing tokens require the offline_access scope when creating the integration on the Nango UI.
• You will need to fetch your Cloud ID to be able to make API requests to the Jira API v3. You can do this with the proxy by calling:

const response = await nango.get({
    endpoint: `oauth/token/accessible-resources`,
    baseUrlOverride: 'https://api.atlassian.com'
});
const cloudId = response.data[0].id;

You can then construct your URL as follows: https://api.atlassian.com/ex/jira/${cloudId}/rest/api/3/<endpoint>

• When you create an OAuth 2.0 (3LO) app, it’s private by default. Before using the integration, you must make your app public. If you want to make your app public, find the how-to here.
• Refresh tokens will expire after 365 days of non use and will expire by 90 days if the resource owner is inactive for 90 days. Make sure you call nango.getConnection() at least every 365 days to trigger a refresh. See reference here.
• Nango also supports BASIC auth for REST APIs in Jira. To use this feature, provide your email as the username and your api_token as the password. To generate an api_token, please refer to the Manage Atlassian API Tokens section
• You will also need to supply your subdomain. When logged into your Atlassian account or Jira instance, look at the URL in your web browser. The subdomain part before .atlassian.net is your Jira subdomain.