Forums

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

New "Service Accounts" and Assets / CMDB

Frank Vandebergh
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 1, 2025

Hi,
We are JSM Premium customer and we want to use the newly released Service Accounts feature. One of the actions we want to perform with this account is call the JSM Assets rest API.

On the Assets schema permissions, we are able to add these service accounts as Users and as Apps. However on the service account itself we need to provide the API token scope and it is not possible to select the cmdb scopes needed for the Asset Management feature. 
Is it possible to perform JSM Assets actions using the new service accounts ? And what is the best way to assign permissions, to the App or User representing this SA ? 


 

2 answers

0 votes
Danyal Iqbal
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 5, 2025

Update 05.09.25
Tested with multiple REST Endpoints >Both classic and Granular API Token scopes do not work with Service Account for Assets REST API.

This is probably a bug.

GET https://api.atlassian.com/ex/jira/orgid/rest/servicedeskapi/assets/workspace -> Status 401
{"code":401,"message":"Unauthorized; scope does not match"}
 
GET https://api.atlassian.com/jsm/assets/workspace/workspaceid/v1/aql/objects -> Status 401
{"code":401,"message":"Unauthorized; scope does not match"}
 
GET https://api.atlassian.com/jsm/assets/workspace/workspaceid/v1/object/object id -> Status 401
{"code":401,"message":"Unauthorized; scope does not match"}
 
GET https://api.atlassian.com/jsm/assets/workspace/workspaceid/v1/objectconnectedtickets/49838/tickets -> Status 401
{"code":401,"message":"Unauthorized; scope does not match"}
 
GET https://api.atlassian.com/jsm/assets/workspace/workspaceid/v1/objectschema/list -> Status 401
{"code":401,"message":"Unauthorized; scope does not match"}

 

0 votes
Pedro Olmo
Community Champion
September 1, 2025

Hello @Frank Vandebergh ,

 

You should set Jira as the product in the token and select the classic model. By selecting these tokens, you should be able to retrieve data from Assets through the REST API.

testst.png

 

Regards

Andreas Stumpf
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 1, 2025

Hi @Pedro Olmo 

Doesn't work here:

Invoke-RestMethod : {"code":401,"message":"Unauthorized; scope does not match"}

Best Regards
Andreas

Loïck DE SOUSA
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 5, 2025

Hi,

I’m experiencing the same behaviour on my side.
Do you have any updates on this topic?

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