✅ Authorization
✅ Read & write data
Tools | Status |
---|---|
Pre-built integrations | ✅ |
API unification | ✅ |
2-way sync | ✅ |
Webhooks from Nango on data modifications | ✅ |
Real-time webhooks from 3rd-party API | ✅ |
Proxy requests | ✅ |
✅ Observability & data quality
Tools | Status |
---|---|
HTTP request logging | ✅ |
End-to-type type safety | ✅ |
Data runtime validation | ✅ |
OpenTelemetry export | ✅ |
Slack alerts on errors | ✅ |
Integration status API | ✅ |
✅ Customization
Tools | Status |
---|---|
Create or customize use-cases | ✅ |
Pre-configured pagination | ✅ |
Pre-configured rate-limit handling | 🚫 (time to contribute: <48h) |
Per-customer configurations | ✅ |
Issues
Pre-Requisites | Status | Comment |
---|---|---|
Paid dev account | ✅ Not required | Free, self-signup for an Atlassian developer account. |
Paid test account | ✅ Not required | Free Jira Cloud instance can be used for testing. |
Partnership | ✅ Not required | |
App review | ⚠️ Conditional | Required only if you want to list your app on the Atlassian Marketplace. |
Security audit | ✅ Not required |
Create an Atlassian developer account
Create a new OAuth 2.0 (3LO) app
Configure OAuth 2.0 (3LO)
https://api.nango.dev/oauth/callback
as the Callback URL.Add API permissions
read:jira-user
- Read user informationread:jira-work
- Read issues, projects, and workflowswrite:jira-work
- Create and update issuesdelete:jira-work
- Delete issuesmanage:jira-project
- Manage project settingsmanage:jira-configuration
- Manage Jira instance settingsoffline_access
- Get refresh tokens (required for long-term access)Obtain your client credentials
Make your app available to users (optional)
Next
Scope | Description |
---|---|
read:jira-user | Read user information |
read:jira-work | Read Jira work items (issues, projects, etc.) |
write:jira-work | Create and update Jira work items |
offline_access | Access to refresh tokens for offline access |
offline_access
scope when creating the integration on the Nango UI.baseUrl
during connection creation (recommended)baseUrl
during connection creation is important if you need to connect to a specific site.
domain
, Nango finds the matching site and sets its cloudId
domain
is specified, Nango uses the first available sitecloudId
and domain
are stored in the connection configurationcloudId
is required for making API requests to the Jira API v3. Nango handles this automatically by matching it to your specified baseUrl
or selecting the first available site. Your API URLs will be constructed as: https://api.atlassian.com/ex/jira/${cloudId}/rest/api/3/<endpoint>
https://api.atlassian.com/ex/jira/${cloudId}/rest/api/3/<endpoint>
nango.getConnection()
at least every 365 days to trigger a refresh. See reference here.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 sectionstate
parameter is required for security in the OAuth flow to prevent CSRF attacks. Nango handles this automatically.