Forums

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

Set an API key with a range

Xiaowen Chen
Contributor
July 10, 2025

I created an API key without scope and was able to successfully obtain the results of the filter.
According to the API documentation, I created an API key with the scopes of read:jira-work and read:issue-details:jira, and called the same API to obtain the results of the filter, but I got a permission issue prompt.
“{
“errorMessages”: [
“A value with ID ‘10363’ does not exist for the field ‘filter’.”
],
“warningMessages”:[]
}”

Do I need to configure any other permissions?

2 answers

0 votes
Karan Sachdev
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 10, 2025

Hey @Xiaowen Chen

If you're creating API Tokens with scope, you will need the following scopes to be able to fetch filter data using APIs:

2025-07-10_16-07-54.png

Thanks!

0 votes
Nikola Perisic
Community Champion
July 10, 2025

Hello @Xiaowen Chen 

This error usually indicates two things:

  • Permission denied for this filter where you don't have permissions to view it
  • Deleted filter is another option that is possible here
Xiaowen Chen
Contributor
July 10, 2025

Hi @Nikola Perisic 
Thanks for your reply.

When I use a key without a scope configured with my account, I can call this API normally.

But once I configure the key with the above - mentioned scope and then call this API, an error occurs.

Both calls are made with the same user account and the same filter. So I don't think the issue lies here.

Do you have any other suggestions?

Nikola Perisic
Community Champion
July 10, 2025

@Xiaowen Chen 

Other than that no, are you using Postman?

Xiaowen Chen
Contributor
July 10, 2025

@Nikola Perisic 

Yes, I am. Could Postman have an impact on the API calls?

Nikola Perisic
Community Champion
July 10, 2025

@Xiaowen Chen 

It shouldn't, could you continue to use the one without scopes?

Xiaowen Chen
Contributor
July 10, 2025

@Nikola Perisic 

If there's really no other way, I'll have to use the one without the scope.

However, using a token without a scope to call the API poses security risks. I'd much rather find a way to use the API with the scope configured properly. 

Suggest an answer

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

Atlassian Community Events