User profile API gives 401 from api.atlassian.com but works with id.atlassian.com

[AJP]

I followed the API documentation to access my user profile via the API as well as eventually finding the (bizarre) way to find my account ID.

On requesting https://api.atlassian.com/users/712...dce/manage/profile it returns a 401 however by looking at the profile UI I see it requests https://id.atlassian.com/gateway/api/users/712...dce/manage/profile successfully.

Does anyone know why is the documented API gives a 401 unauthorised when the undocumented API is working without problem?

[Sunny Ape]

Hello @AJP 

The reason you can't access that endpoint is because it's part of the Atlassian Cloud Admin APIs that are restricted to only being accessible by your organisation's admins.

For your personal account ID, just use the various Myself endpoints, such as:

GET

https://<your_domain>.atlassian.net/rest/api/3/myself 

[Alexandre Fischer]

Hello,

I'm facing the same issue with scoped tokens. it works perfectly for tokens without scopes.

I added "read:jira-user" scope to my token as described in the documentation.

I tried these two endpoints:

• https://<my-domain>.atlassian.net/rest/api/3/myself
• https://api.atlassian.com/ex/jira/<cloud-id>rest/api/3/myself

And still have the 401 error with this lovely message:

• Client must be authenticated to access this resource.

If someone can help

Thanks in advance

Best regards

[Brandon Viertel]

Some scopes seem to be misleading or non-functional. When accessing an app's API (Jira, Confluence), the scopes for the APIs work great. When accessing the Atlassian Admin API (where I think this would be extremely beneficial for security), it needs to authenticate as Org Admin with an un-scoped API token. Even enabling all available scopes it still fails, even as an Org Admin.