Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

REST API documentation required scopes not found

KC Wong
Contributor
August 27, 2026

Get issue property REST API (https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-properties/#api-rest-api-3-issue-issueidorkey-properties-propertykey-get) states it requires either: 

Classic - read:jira-work
Granular - read:issue.property:jira

But when I tried to create an organizational REST API token with scope, none of those can be found. 

1 answer

1 accepted

0 votes
Answer accepted
Trudy P Claspill
Community Champion
August 27, 2026

Hello @KC Wong 

Are you trying to create a token through https://admin.atlassian.com ?

If so are you trying to create it through Organization Settings > API Keys ?

That would not be the correct location. Those keys are only for accessing the Organization Admin API.

For the API you are trying to use you need a personal API token or a token created for a Service Account.

https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/

https://support.atlassian.com/user-management/docs/understand-service-accounts/

 

Trudy P Claspill
Community Champion
August 27, 2026

Hello @KC Wong 

I see that you accepted my answer.

Were you successful in creating the scoped API token for a service account or as a personal access token? And then successful in using that token with the API call?

KC Wong
Contributor
August 27, 2026

Yes, I thought all types of tokens share the same list of scopes. I switched to use an OAuth2 token of a service account.

Now I need to figure out which scope allows me to use the overrideEditableFlag in Edit Issue REST API. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events