Missing scopes for Folder APIs in Manage API tokens for your Atlassian account

[karan]

Here’s the grammatically corrected and professionally formatted version of your message:

---

While creating an API token with scopes via Create Atlassion token API, I noticed that folder-related REST API scopes for Confluence are not listed.

I am trying to fetch folders by their IDs using the documented API:

Get folder by ID
api-folders-id-get 

In that documentation, the required scope is mentioned as:

read:folder:confluence

However, this scope is not available in the dropdown list when generating an API token.

---

Let me know if you'd like this version tailored for Atlassian Community or Jira ticket format.

[karan]

Hi @Marc - Devoteam

Yes, but this scope is not listed when creating an Atlassian API token with scopes for the Confluence product, even though it is mentioned in the REST API documentation: read:folder:confluence

I’d like to know which alternative scope (if any) from the available list can be used to access the same API, or if there's another recommended approach to achieve this?

because using Atlassion token without scope it works.

[Marc - Devoteam]

Hi @karan 

I see where I was wrong, but I think you will need to global read:confluence:content

Otherwise raise your question at Atlassian Support

[Marc - Devoteam]

Hi @karan 

You asked the same question for others in the JSM forum.

"Scopes are essentially permissions that specify what an application can do with Jira Service Management"

Scopes relate tgo app integrations, not affecting the regular API actions that can be executed by a user with a token, dependent on rights in an application