Organization API Key unable to access the User management APIs

[madhu kumar telugu]

I have created Organization API Key when I use the API Key to access the user management APIs getting 403 response 

curl --location 'https://api.atlassian.com/admin/v1/orgs/<ORG_ID>/users' \

--header 'Authorization: ••••••'

{

"timestamp": "2025-06-06T06:03:27.122+00:00",

"path": "/api/admin/v1/orgs/<ORG_ID>/users",

"status": 403,

"error": "Forbidden",

"message": "User has no permission to access resource.",

"requestId": "b4fce632-202784"

}

While creating the Key i don't see any scopes related to read:jira-user or groups. 

[Jaime Escribano]

Hi @madhu kumar telugu and welcome to the community!

Is your user a site-admin or and org-admin? You API token only has as many permissions as the user you use through the UI. 

You could also try going through this tutorial step by step, as you might be missing some step relating to Authentication along the way -> Add user to group

Regards,

Jaime Escribano

[madhu kumar telugu]

Thanks Jaime. The User logged in has org-admin group but when I create the org API Key the available scopes doesn't include any user management APIs.

[Jaime Escribano]

Turn's out lot's of people are having a similar issue

(example: API Token authentication failing. What am I doing ...)

You have generated a Oauth 2.0. Token which is pretty new and not well documented. 

The endpoints have changed their structure.

For example in Confluence it has changed from  

https://your-domain.atlassian.net/{api}

to

https://api.atlassian.com/ex/confluence/{cloudid}/{api}

Some extra info (not comprehensive) can be found here:

OAuth 2.0 (3LO) apps


So my suggestion would be to generate a new legacy token to avoid confusion 😊