What is Atlassian Connect?

You can use the Atlassian Connect framework to build add-ons for Atlassian applications like JIRA and Confluence. An add-on could be an integration with another existing service, new features for the Atlassian application, or even a new product that runs within the Atlassian application. You can also create add-ons for HipChat. To learn how, check out the HipChat add-on documentation.

What is an Atlassian Connect add-on?

Simply understood, Atlassian Connect add-ons are web applications. Atlassian Connect add-ons operate remotely over HTTP and can be written with any programming language and web framework.

Fundamentally, Atlassian Connect add-ons have three major capabilities:

  1. Insert content in certain defined places in the Atlassian application's UI.
  2. Make calls to the Atlassian application's REST API.
  3. Listen and respond to WebHooks fired by the Atlassian application.

What does an Atlassian Connect add-on do?

  • Declare itself with a descriptor. The add-on descriptor is a JSON file that tells the Atlassian application about the add-on. In the descriptor, an add-on declares where it is hosted, which modules it intends to use, and which scopes it will need.
  • Extend the Atlassian application UI with modules. The features that an add-on can use within the Atlassian application are called modules. There are modules for general pages in the application or more specific locations, like panels in JIRA issues or macros in Confluence pages. Refer to the full module lists for JIRA and Confluence.
  • Request appropriate scopes. Your add-on must specify what type of access it needs from the Atlassian application. You declare required scopes for the add-on in the add-on descriptor file. Scopes determine which REST API resources the add-on can use.
  • Recognize the user. Atlassian Connect add-ons authenticate users via JWT, so each request from the Atlassian application to your add-on contains details about the user currently viewing that page. This allows you to serve the right context, respect necessary permissions and make other decisions based on the user's identity.
  • Call the Atlassian application's REST API. Your add-on can retrieve data or push information to the Atlassian host application (for example, to build reports and create issues).
  • Respond to the Atlassian application's webhooks. Your add-on can receive notifications when certain events occur with webhooks, like when a JIRA issue changes status. The webhook payload contains information about the event, allowing your add-on to respond appropriately.
  • Register on the Atlassian Marketplace. List your add-on in the Marketplace to make it installable. You can list your add-on privately on the site if you don't intend to sell or distribute your code, but all Connect add-ons need to be listed in order to be installable. Private listings are supported with secret tokens that you can generate yourself.
  • Respect add-on licensing. Every request from the Atlassian application to your add-on contains the add-on license status for that instance. Your add-on can respond appropriately, for example, by alerting the user, locking down functionality, or encouraging an upgrade.

How does Atlassian Connect work?

To an end user, your add-on should appear as a fully integrated part of the Atlassian application. Once your add-on is registered with the application, features are delivered from the UI and workflows of the host application. This deep level of integration is part of what makes Atlassian Connect add-ons so powerful.


Most Atlassian Connect add-ons are implemented as multi-tenanted services. This means that a single Atlassian Connect add-on will support multiple subscribing Atlassian applications. For more information, see Understanding Atlassian in the cloud.


Security is critical in a distributed component model such as Atlassian Connect. Atlassian Connect relies on HTTPS and JWT authentication to secure communication between your add-on, the Atlassian product and the user.

Your add-on's actions are constrained by well-defined permissions. Your add-on can only perform activities it declares in its descriptor. These permissions are granted by Atlassian application administrators when they install your add-on. Examples of permissions include reading content, creating pages, creating issues, and more. These permissions help ensure the security and stability of cloud instances.

Read our security overview for more details.


Since Atlassian Connect add-ons can insert content directly into the Atlassian host application, it is critical that add-ons are visually compatible with the Atlassian application's design. To help developers, Atlassian's design team has created detailed design guidelines and a library of reusable front-end UI components.

Let's get started

If you made it this far, you're ready to write your first Atlassian Connect add-on! Follow the link below to get started.