What Scopes are needed to use the Team Members Public API

[Robert Condon]

I am trying to use the The Teams REST API using a Service Account, but don't know what scopes to apply?
The documentation doesn't list which ones to use, as it normally does

I can create a personal token with no scopes, which works, but as soon as I try to apply scopes on a Service Account or user account, I can't seem to find the correct ones. 
I cannot create a scopeless Service Account API key, and ideally don't want to rely on a user generated key for work that sits in production. 

This is the endpoint -https://api.atlassian.com/public/teams/v1/org/{orgId}/teams/{team}/members

The scopes I have tried

view:team:teams

view:membership:teams

read:account

manage:org

[Bill Sheboy · Accepted solution]

Hi @Robert Condon 

Here is the open suggestion in JAC to allow the Teams REST API endpoints to work with a service account: https://jira.atlassian.com/browse/JRACLOUD-96410

Kind regards,
Bill

[Robert Condon]

Thanks for linking the Feature request, fingers crossed

[Arkadiusz Wroblewski · Accepted solution]

@Robert Condon 

This API must be called with basic auth/ using a normal Atlassian API token, not with OAuth scopes.

Team Public Rest API  

Service accounts won't work here.

[Robert Condon]

That's very frustration, especially from an Enterprise perspective