Hi everyone,
I’m working on an integration with Jira Assets to map and manage Asset Object IDs programmatically within our internal systems.
To start, I retrieved the accessible resources for my OAuth token via:
GET https://api.atlassian.com/oauth/token/accessible-resources
(Ref: OAuth: Making calls to the API)
This returned only one workspace ID:
2757c183-6382-412d-95f2-78cd42304992
When I try using that workspace ID with the Assets API:
GET https://api.atlassian.com/jsm/assets/workspace/2757c183-6382-412d-95f2-78cd42304992/v1/object/aql
I get a 404 Not Found.
Then, I inspected the Assets section in the Jira UI (via browser DevTools) and found a different workspace ID being used:
d347fa2c-2d9f-43e6-88ad-4fcf1b527b5b
This seems to be the correct one associated with Assets in our environment.
However, when I try to use that ID in the same API call:
GET https://api.atlassian.com/jsm/assets/workspace/d347fa2c-2d9f-43e6-88ad-4fcf1b527b5b/v1/object/aql
I receive a 401 Unauthorized error — even though my app is authenticated and working for other Jira APIs.