Hi everybody, I am a managed user in our Jira Cloud instance (basic Atlassian plan). I am part of a group with the 'view project' (Browse Projects) permission, and I have Jira Software access as a user. API token access is enabled for users in our organization. * I can view projects and issues via the Jira UI. * API requests using Basic Auth (email + API token) to the REST API v3 consistently fail, either with authentication failure or I get empty results (no projects or issues). What I've checked: * My group roles and permissions include 'Browse Projects' * I am licensed for Jira Software * API token access is explicitly allowed for managed users * I am using the correct API token and registered email address Question: Are there additional global/project permissions, security settings, or managed account policies that could prevent a managed user (with correct UI and group access) from authenticating and accessing issues via Jira REST API on the basic plan? Any guidance on how to ensure I can successfully use REST APIs to fetch Jira issues and data would be appreciated. Thanks in advance!

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What Permissions or Setup Are Needed for a Managed User to Use Jira Cloud REST API on Basic Plan?

Yash Bhatia

Hi everybody,

I am a managed user in our Jira Cloud instance (basic Atlassian plan). I am part of a group with the 'view project' (Browse Projects) permission, and I have Jira Software access as a user. API token access is enabled for users in our organization.

I can view projects and issues via the Jira UI.
API requests using Basic Auth (email + API token) to the REST API v3 consistently fail, either with authentication failure or I get empty results (no projects or issues).

What I've checked:

My group roles and permissions include 'Browse Projects'
I am licensed for Jira Software
API token access is explicitly allowed for managed users
I am using the correct API token and registered email address

Question:
Are there additional global/project permissions, security settings, or managed account policies that could prevent a managed user (with correct UI and group access) from authenticating and accessing issues via Jira REST API on the basic plan?

Any guidance on how to ensure I can successfully use REST APIs to fetch Jira issues and data would be appreciated.

Thanks in advance!

Accepted answers

Gor Greyan

Hi @Yash Bhatia

Welcome to the Atlassian Community!

Did you check the Security Levels? Maybe there is a Security Level set for the issue, which you are trying to use.

All comments

Gor Greyan

Hi @Yash Bhatia

Welcome to the Atlassian Community!

Did you check the Security Levels? Maybe there is a Security Level set for the issue, which you are trying to use.

Yash Bhatia

Hey @Gor Greyan

Thank you for your prompt response!

However, I have tried accessing multiple issues and consistently receive a 401 Unauthorized error, even when calling the /rest/api/3/myself endpoint. Does this suggest that the problem is broader and likely related to my overall permissions or authentication setup, rather than specific issue restrictions.

Gor Greyan

Dear @Yash Bhatia

Here are some points, that you can double check.

Use an API token, not a password
Go to [id.atlassian.com → Security → API tokens → Create API token]*.
Postman → Authorization tab → Basic Auth:
Username = Atlassian account email
Password = API token
(Not the normal Atlassian password.)
Make sure Postman is sending the header
Authorization: Basic <base64(email:api_token)>
IP allowlisting: if the org uses IP allowlists, their machine’s IP must be added.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

rest-api

jira-cloud