https://api.atlassian.com/jsm/ops/api - "This endpoint does not accept service accounts."

[Steven Hubau]

The ops API does not accept service accounts, is this a bug or deliberate setting? If so, why? 

[Aaron Pavez _ServiceRocket_]

Hi @Steven Hubau 

Which API are you trying to use?

https://developer.atlassian.com/cloud/jira/service-desk-ops/rest/v2/intro/#status

The one you shared is not complete:

URL format

The Jira Service Management operations REST API uses a consistent URL pattern to access different resources. The general format is as follows:

https://api.atlassian.com/jsm/ops/api/{cloudId}/{version}/{domain}

Let us know which API in the docs are you trying to use.

Regards

[Steven Hubau]

https://api.atlassian.com/jsm/ops/api/{cloudId}/v1/schedules and https://api.atlassian.com/jsm/ops/api/{cloudId}/v1/alerts

[Aaron Pavez _ServiceRocket_]

Does the service account have these permissions?

Permissions required: Permission to create a schedule:

• the user has edit configuration rights.
• the user is the admin of the team that the schedule belongs to.

OAuth 2.0 scopes required:

read:ops-config:jira-service-management

write:ops-config:jira-service-management

Regards

[Aaron Pavez _ServiceRocket_]

If you have the permissions, then try the Oauth credential:

https://support.atlassian.com/user-management/docs/create-oauth-2-0-credential-for-service-accounts/

If this still doesn't work, that OPS endpoint doesn't support services accounts yet.

I can't find anything related to that, though, but probably that's the problem.

Regards

[Steven Hubau]

I am unable to add service accounts as member or admin of the team, maybe that is the problem? 

[Bill Sheboy]

Hi @Steven Hubau 

Correct; based on this defect, it is not possible to add a service account as a team member: https://jira.atlassian.com/browse/ATLAS-269

Kind regards,
Bill