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; } } }

What scope should I choose to define a token authorized to use the 'Team Public REST API'?"

jvigeant

When I use the Team Public REST API with a token that has no scope to list a team's members, it works.

I'd like to do the same with a "token with scope", but I can't find a granular or classic scope to do that.

I looked at the token creation in the security menu on my profile and tried to create an app on the developer console, but there was no scope like "read:team:teams".

Thanks for your help.

Accepted answers

Marc -Devoteam-

Hi @jvigeant

Welcome to the community.

If the API endpoint has no granular scopes defined, this means that a scoped API token can't be used.

A normal API token will need to be used.

All comments

Marc -Devoteam-

Hi @jvigeant

Welcome to the community.

If the API endpoint has no granular scopes defined, this means that a scoped API token can't be used.

A normal API token will need to be used.

jvigeant

Hi,

Thanks for your reply.

My goal is to use a service account that lets me specify a read-only scope for my API automation. One of my initial requirements is to list team members so I can tag them.

I will use my own token for the first time. I hope that in the future we'll be able to either directly mention a team in automation or define a scope for the team in a token definition.

Marc -Devoteam-

Hi @jvigeant

Please accept my answer as a solution, if my answer helped to solve or provide a workaround to your request.

This will help other community member trying to solve the same or provide them with a work around

P.S. If the answer is very valuable to you, please share some kudos.

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