Are there any up-to-date docs showing the correct endpoint/scopes needed for the Teams API?

[jcardozo]

Has anyone successfully used the Teams API with OAuth 2.0 (3LO)?

I’m running into a “token mismatch / unauthorized” error no matter what scopes I try.

Here’s what I’ve tried so far:

• Switched from the old URL (https://api.atlassian.com/jsm/ops/api) to https://api.atlassian.com/ex/jira/ — which works for schedules, on-call schedules, and contact info, but not for teams.

• Scopes tested:

  • read:ops-config:jira-service-management
  • read/write:ops-config:jira-service-management
  • All the classic scopes

• Confirmed that Teams are enabled in JSM.

[Marc - Devoteam]

Hi @jcardozo 

Welcome to the community.

Going over the documentation you can't use a scoped token for Teams.

You can only execute cals with scoped tokens, if there are granular scopes mentioned on the API endpoint, like on: api-rest-api-3-issue-post 

[jcardozo]

Hi @Marc - Devoteam! Thanks for the response. I’m specifically asking about the JSM On Call Teams API, which lists read:ops-config:jira-service-management as the required scope. I believe this is a relatively new endpoint and might still be missing some documentation details.

[Marc - Devoteam]

Hi @jcardozo 

I provided that in the link I shared as an example.

This API doesn't have "granular" scopes for the endpoints in the API.

Not every API from Atlassian has the option to use a scoped token.

If a scoped token can be used the scoped option are listed under "granular", if it only states "OAuth 2.0 scopes", then you can't use a scoped token.