Trouble accessing service-desk-ops api with service account

[Michał Maciaszek]

Hi,

I am using my service account token (it has proper accesses granted) to do stuff with Jira, but also check teams on call schedules etc.

It works properly for Jira api, where I am using this base url:

“https://api.atlassian.com/ex/jira/{cloud_id}”

But when I am trying to check stuff from service-desk-ops, API I am getting 401 unauthorized.

The documentation ask for customerID, but I am not sure what that is, and why is that different that cloudID?

https://developer.atlassian.com/cloud/jira/service-desk-ops/rest/v2/intro/#authentication-for-other-integrations

I am getting:
RuntimeError: Failed to list Jira Ops teams: 401 Client Error: Unauthorized for url: ``https://api.atlassian.com/ex/jira/{cloud_id_masked}/jsm/ops/api/v1/teams/{team_id_masked}/roles

1. How do I get the customerID? What is that, or is it just old documentation, and no one noticed it?
2. Is the URL I am using okay? The authentication I am using (bearer token in header) should be working fine, since it works for Jira stuff.

[Arkadiusz Wroblewski]

Hello Michał,

The URL naming (`customerId` vs `cloudId`) isn't the issue, both use your standard cloud site identifier. You are likely hitting a known native limitation: JSM Operations endpoints do not support service accounts (JSDCLOUD-17685). This explains why your token works for normal Jira REST APIs but fails here. 😉

To verify, test the endpoint using a standard licensed user account with the `read:ops-config:jira-service-management` scope. If that succeeds, you are definitely hitting this platform blocker. I'd recommend watching that public ticket for updates.

Best,
Arkadiusz🤠