nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

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

Accepted answers

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:

<a href="https://api.atlassian.com/jsm/ops/api/%7BcloudId%7D/%7Bversion%7D/%7Bdomain" target="_blank" rel="nofollow noopener noreferrer">https://api.atlassian.com/jsm/ops/api/{cloudId}/{version}/{domain</a>}

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

Regards

All comments

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:

<a href="https://api.atlassian.com/jsm/ops/api/%7BcloudId%7D/%7Bversion%7D/%7Bdomain" target="_blank" rel="nofollow noopener noreferrer">https://api.atlassian.com/jsm/ops/api/{cloudId}/{version}/{domain</a>}

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

Regards

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management