API Token

Setup
Reference

What You'll Need

Credential	Description
API Token	Generated from Atlassian account settings
Email Address	Your Atlassian account email
Base URL	Your Jira instance URL (e.g., `https://your-company.atlassian.net`)
Domain	Your Atlassian domain (e.g., `your-company.atlassian.net`)
Organization ID	Your Atlassian organization ID

Overview

API Token authentication uses Basic Auth with your Atlassian email and a generated token. This provides secure, automated access to Jira Cloud APIs.

Prerequisites

User Permissions

The user creating the API token needs these permissions:

Global permission: Administer Jira
Project permission: Browse Projects

For full data access, use an account with Jira Administrator privileges.

Org-Wide Settings

Ensure all user emails are set to Visible by “Anyone”:Users configure this in their Atlassian account settings under Profile and visibility → Contact.

Setup Guide

Access API Token Settings

Navigate to the Atlassian API Token Management page.Sign in with your Atlassian account credentials.

Create an API Token

Click Create API token
Enter a meaningful label: Parable Integration
Click Create

Copy your now!This is the only time it will be displayed. Store it in a secure password manager before closing this page.

Find Your Organization ID

Go to Atlassian Admin Console
Look at the URL: https://admin.atlassian.com/o/{ORG_ID}/...
Copy the ORG_ID value

Note Your Instance URL

Your Jira instance URL follows this pattern:

https://your-company.atlassian.net

Find this in your browser’s address bar when viewing Jira.

Verify Your Setup

The API uses Basic authentication. Combine your credentials and Base64 encode them:

username:password  →  Base64 encode  →  Authorization: Basic {encoded}

# The -u flag handles Base64 encoding automatically
curl -X GET "{endpoint}" \
  -u "your-email@company.com:YOUR_API_TOKEN" \
  -H "Content-Type: application/json"

For , use your email address as the username and the API token as the password.

Success! If you received a 200 OK response with valid data, your credentials are configured correctly. You can now proceed to configure this connector in Parable.

Permissions Reference

Endpoint	Required Permission	Data Accessed
`/rest/api/3/search/jql`	BROWSE_PROJECTS	Issues via JQL
`/rest/api/3/project/search`	BROWSE_PROJECTS	Project list
`/rest/api/3/users`	ADMINISTER	User information
`/rest/api/2/auditing/record`	ADMINISTER	Audit logs

Rate Limits: enforces rate limits of .Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.

Troubleshooting

Error	Meaning	Solution
401 Unauthorized	Invalid credentials	Verify email and token are correct
403 Forbidden	Insufficient permissions	Check user has BROWSE_PROJECTS and ADMINISTER permissions
429 Too Many Requests	Rate limit hit	Reduce request frequency; implement backoff

Common Issues

”User not found” when querying users

Ensure the user’s email visibility is set to “Anyone” in their Atlassian profile settings.

Token created but not working

Wait 5-10 minutes for the token to propagate across Atlassian’s systems.

Additional Resources

Jira Cloud REST API

Official API documentation

Basic Auth Guide

Atlassian authentication guide

Connectors

Encryption

What You'll Need

Overview

Prerequisites

Setup Guide

Verify Your Setup

Permissions Reference

Troubleshooting

”User not found” when querying users

Token created but not working

Additional Resources

Jira Cloud REST API

Basic Auth Guide

Connectors

Encryption

What You'll Need

​Overview

​Prerequisites

​Setup Guide

​Verify Your Setup

​Permissions Reference

​Troubleshooting

​”User not found” when querying users

​Token created but not working

​Additional Resources

Jira Cloud REST API

Basic Auth Guide

Overview

Prerequisites

Setup Guide

Verify Your Setup

Permissions Reference

Troubleshooting

”User not found” when querying users

Token created but not working

Additional Resources