Error in search groups API: This is in Atlassian admin api

[Sumit Rajendra Athani]

API document link: 

https://developer.atlassian.com/cloud/admin/organization/rest/api-group-groups/#api-v1-orgs-orgid-groups-search-post

We are getting the following error while calling the api and this error code is not specified in the api documentation .

{

"errors": [

{

"code": "ADMIN-401-2",

"status": "401",

"title": "INSUFFICIENT_SCOPE",

"detail": "Insufficient scope. Create a new API Key for your Organization https://support.atlassian.com/organization-administration/docs/manage-an-organization-with-the-admin-apis/"

}

]

}

Also, 

we had created a API key long back and the API worked for the old key. But when the same user created another API key , the API did not work with the new API key. And got the same above error.

[Paulo Ramalho]

Sumit, you are affected by this bug: https://jira.atlassian.com/browse/ID-8782

Atlassian said they will be rolling a fix by Friday, but no guarantees.

[Marc - Devoteam]

Hi @Sumit Rajendra Athani 

As @Florian Bonniec mentions, what are the permission on the user related to the API token?

This user, will need to have Org admin permission to use this API endpoint.

[Sumit Rajendra Athani]

hi @Marc - Devoteam , The user is org admin

[Florian Bonniec]

HI @Sumit Rajendra Athani 

401 is permission error. The token/account you use do not have enough permission.

Regards

[Sumit Rajendra Athani]

hey @Florian Bonniec , Where and how can we grant permission to the apiKey that is generated? 

else how to generate token with correct permissions? because we are already org admin here when we created the api key.

[Sumit Rajendra Athani]

https://developer.atlassian.com/cloud/admin/organization/rest/api-group-groups/#api-group-groups

on the same docs, other apis like get events, get orgs are working. 

[Florian Bonniec]

You have to create a token for this purpose with an account that have org admin permission.

Manage an organization with the admin APIs | Atlassian Support

Regards

[Sumit Rajendra Athani]

Hi @Florian Bonniec , the token was created with an org admins account itself. And as mentioned the api worked with an older apikey, but failed with an new apikey when created by the same user as previous.