Atlassian (Jira, Confluence)
ModerateAn OAuth 2.0 (3LO) integration is self-serve: create it in the developer console, toggle sharing, and any Atlassian user can authorize it the same day, though unapproved apps show a 'not reviewed by Atlassian' warning.
Agent-researched, not yet reviewed by a personResearched 2026-10-20
Working in dev
30–90 min
Signing in with your own account
Any user can connect
Same day–3 weeks
A shared 3LO integration that reads and writes Jira/Confluence data; sharing alone is same day with a warning, and the upper bound covers Atlassian approval to remove the warning and a per-tenant rate-limit pool.
- Waiting on
- Nothing to go live. Optionally, Atlassian app approval (a staff post cited a 10-business-day objective) and review for the per-tenant rate-limit pool.
- Cost
- No fees found in the docs
What you need first
An Atlassian account and an Atlassian Cloud site (a free Jira/Confluence site works) for testing
The consent screen makes the user pick a site, and API calls are made against that site's cloudid.
A single distributable app for all customers, not one 3LO app per customer and not customer-generated API tokens
Atlassian's June 2025 guidance says per-customer 3LO apps and stored customer API tokens violate its standards, and non-compliant apps may lose platform access.
A decision between OAuth 2.0 (3LO), Forge and Connect
3LO is hosted by you and suits accessing data on behalf of a user from an external service. Forge is Atlassian-hosted, installed by site admins, and the only type accepted for new Marketplace submissions since Sep 17, 2025. Connect is legacy and not recommended for new apps.
A test instance of your product for reviewers, if you seek approval or a listing
Marketplace reviewers need to run through setup and configuration.