APIs & Integrations
Atlassian
Overview
Pre-built tooling
Pre-built use-cases
No pre-built use cases yet (time to contribute: <48h)
Not seeing the use case you need? Build your own independently.
Access requirements
Pre-Requisites | Status | Comment |
---|---|---|
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
Useful links
Contribute useful links by editing this page
API gotchas
- **To allow the possibility of refreshing the token, you must add
offline_access
to your scopes when creating the integration on the Nango UI.** - 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. - When using the proxy for atlassian, it is important to know that Jira apps will use
/jira/{cloudid}/{api}
for jira apps and/confluence/{cloudid}/{api}
for confluence apps.
Contribute API gotchas by editing this page