Jira Software Cloud API Authentication

How to authenticate Jira Software Cloud API requests: one Bearer API key plus a connectionId. MindCloud runs the OAuth flow and refreshes tokens for you.

Every Jira Software Cloud API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Jira Software Cloud account. This page covers both, plus exactly how to send them, so you do not need to visit any other page to get authenticated.

Steps to authenticate

Create a MindCloud account at app.mindcloud.co if you do not already have one.
Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
Create a Jira Software Cloud connection in Connections. Jira Software Cloud uses OAuth. When you create the connection, you are redirected to sign in to Jira Software Cloud and approve access — MindCloud stores the resulting tokens and refreshes them automatically, so your integration never has to.
Copy the connection’s connectionId — you will send it on every request alongside your MindCloud API Key.

How requests are authenticated

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Jira Software Cloud account that should run the action. MindCloud stores and refreshes the Jira Software Cloud credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions.

For example, calling Accessible Resources with an Jira Software Cloud connection looks like this:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/jiraSoftwareCloud/latest/actions/accessible-resources" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

The Authorization: Bearer <your MindCloud API Key> header authenticates you to MindCloud; the connectionId tells MindCloud which Jira Software Cloud account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Connect Jira Software Cloud

You need access to the Atlassian developer console and a Jira Cloud site you can authorize.

Open the Atlassian developer console
Sign in to developer.atlassian.com, open Developer console, and create a new OAuth 2.0 (3LO) app if you do not already have one for this integration.
Developer console
Configure OAuth 2.0 authorization
Open Authorization in the left menu, select Configure next to OAuth 2.0 (3LO), enter the callback URL `https://api.mindcloud.co/v1/oauth/jira/callback`, and save your changes.
Developer console → Authorization
Add Jira API permissions
Open Permissions in the left menu, add the Jira Cloud platform REST API, and grant these scopes: `read:jira-user`, `read:jira-work`, `write:jira-work`, `manage:jira-project`, and `offline_access`.
Developer console → Permissions
Copy your client credentials
Open Settings for the app and copy the Client ID and Secret. You will use these values when you create or update the MindCloud test connection for Jira Software Cloud.
Developer console → Settings

Keep your key safe

Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs. Anyone with the key can call the Universal API as your MindCloud account, across every connection you have created.