Skip to main content

Overview

Pre-built tooling

ToolsStatus
Pre-built authorization (Basic)
Pre-built authorization UI
Custom authorization UI
End-user authorization guide
Expired credentials detection
ToolsStatus
Pre-built integrations
API unification
2-way sync
Webhooks from Nango on data modifications
Real-time webhooks from 3rd-party API🚫 (time to contribute: <48h)
Proxy requests
ToolsStatus
HTTP request logging
End-to-type type safety
Data runtime validation
OpenTelemetry export
Slack alerts on errors
Integration status API
ToolsStatus
Create or customize use-cases
Pre-configured pagination🚫 (time to contribute: <48h)
Pre-configured rate-limit handling🚫 (time to contribute: <48h)
Per-customer configurations

Pre-built integrations

EndpointDescriptionReadme
GET /teams-listFetch teams in an organisation in Jira🔗
EndpointDescriptionReadme
POST /usersCreates a user in Jira. Note that this endpoint is marked as experimental and could
be deprecated in the future. Products are optional and allowed params are
jira-core, jira-servicedesk, jira-product-discovery, jira-software. Defaults to
jira-software. Note that the last name isn’t able to be set via the API and
the first name defaults to the email address.
🔗
DELETE /usersDeletes a user in Jira. Note that this endpoint is marked as experimental and could
be deprecated in the future.
🔗
GET /usersFetches a list of users from Jira🔗
Not seeing the integration you need? Build your own independently.

Access requirements

Pre-RequisitesStatusComment
Paid dev account
Paid test account
Partnership
App review
Security audit

Setup guide

No setup guide yet.
Need help getting started? Get help in the community.
Contribute improvements to the setup guide by editing this page
Contribute useful links by editing this page

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.
Contribute API gotchas by editing this page

Connect to jira-basic

Guide to connect to jira-basic using Nango Connect.
I