Teams GraphQL API OAuth Scopes - Can't Configure in Developer Console

[Brynjar Hauksson]

 Hey everyone! I'm running into a pretty frustrating issue with the Teams GraphQL API and hoping someone here has encountered this before or can point me in the right direction.

The Problem

I'm trying to integrate with Atlassian's Teams GraphQL API, and I've discovered something interesting - the OAuth scopes for Teams API definitely exist and the system recognizes them, but I can't actually configure them in my app's permissions settings. When I try to make requests with the Teams API scopes, I get this very specific error message:

This app has requested User identity API & Teams API scopes that have not been added to the app. Configure the app at https://developer.atlassian.com/apps and add the following scopes to the User identity API & Teams API: manage:org, view:membership:teams, view:team:teams.

What's interesting here is that the OAuth system clearly knows about these scopes - it's telling me exactly which ones I need (view:team:teams, view:membership:teams, and manage:org) and even directing me to the developer console to configure them. But when I actually go to my app's permissions page, these scopes are nowhere to be found in the available options.

I've done quite a bit of testing to validate that the API itself is working. The GraphQL schema introspection shows all the Teams API types like TeamV2 and TeamMemberV2, and when I use Atlassian's official GraphQL Explorer, I can successfully run queries like this one that retrieves team members:

query GetTeamMembers($teamId: ID!, $siteId: String!) {  team {    teamV2(id: $teamId, siteId: $siteId) {      id      displayName      members {        edges {          node {            member {              accountId              name              picture            }            state            role          }        }      }    }  }}

The query works perfectly in the official explorer, returning complete team member data. This confirms that the API functionality is there and working - I just can't access it through OAuth because I can't configure the necessary scopes.

What I've Tried

I've spent quite a bit of time investigating this, and I'm pretty confident the issue is on the configuration side rather than my implementation. Through testing different query patterns, I noticed something interesting: when I try direct queries like teamV2(id: "...", siteId: "..."), I get "Field undefined" errors, which suggests the fields are completely hidden. But when I use the nested pattern like team { teamV2(...) }, I get the specific OAuth scope errors mentioned above. This tells me the API is actually designed to work with third-party OAuth - it's just that I can't configure the necessary scopes.

I've tried a few workarounds without success. Adding the scopes manually to the OAuth authorization URL gets blocked because they're not configured in the app. I looked for alternative REST endpoints for Teams data but couldn't find any. The GraphQL approach seems to be the intended path forward, which makes sense given that Atlassian has been pushing GraphQL as the modern API approach.

My Questions

So here's what I'm wondering - has anyone else run into this issue? Are these scopes maybe in some kind of beta or preview mode that requires special access? I noticed that the error message specifically mentions "User identity API & Teams API" which makes me think there might be some additional configuration step I'm missing.

I'm also curious if this might just be a UI bug in the developer console. The OAuth system clearly knows about these scopes and can validate them, so maybe they're supposed to be showing up in the permissions interface but aren't due to some display issue?

Another possibility I'm considering is whether there are prerequisites for accessing these scopes. Maybe you need to have certain other permissions configured first, or there's an application process for Teams API access that I'm not aware of.

Current Status

Right now I'm pretty much stuck. I have a working GraphQL query that I've validated in the official explorer, I understand the OAuth flow and error handling, and my implementation is ready to go. The only blocker is getting these three scopes configured: view:team:teams for basic team data access, view:membership:teams for member information, and potentially manage:org if I need role assignment data.

Has anyone successfully integrated with the Teams GraphQL API using OAuth? If so, I'd love to hear how you got access to these scopes. Or if you've seen similar issues with other Atlassian APIs, maybe there's a pattern here I'm missing.

Any guidance would be really appreciated! This seems like it should be a straightforward integration once the OAuth configuration is sorted out.

[Trisha Griffis]

Many developers report that required Teams scopes are not visible in the Developer Console, despite being named in error messages and GraphQL responses.

To my knowledge there’s no way to add these scopes through the standard UI, suggesting they’re either restricted or part of an internal or beta feature

Official Atlassian Guidance: 

• The Teams GraphQL API (including queries like teamSearchV2) is marked as Beta. You must include the headers:

{ "X-ExperimentalApi": ["teams-beta", "team-members-beta"] }

• to access team and team member fields. 

• For REST-based alternatives, Atlassian provides a Public Teams REST API. However, this is restricted to Basic Auth with API tokens, and notably not accessible by OAuth2 or Forge apps.

Why the Scopes May Be Hidden

• These scopes appear to belong to internal or early-access APIs, that’s why they aren’t exposed in the standard Developer Console. It’s likely Atlassian hasn’t opened them for public app use yet.

• Until Atlassian expands access or enables them for external use, you won’t be able to request these scopes from your OAuth app, even though the GraphQL schema references them. 

What You Can Do Now 

• If you’re building integrations that need Teams data, consider filing a feature request or support request on Atlassian Developer Community or Jira (such as in the ECO project) to surface this ask and gather votes.

• As a fallback, explore using the Public Teams REST API with API tokens—where feasible and supported.

Yes, the OAuth scopes for Teams (view:team:teams, etc.) exist in the API layer, but they do not appear in the Developer Console because access is limited. These endpoints are still in beta/internal mode. Use the X-ExperimentalApi headers or the REST API (via API token) as a workaround, and consider requesting public access via official feedback channels.