403 not authorized when connecting to API with scoped token

[David Soucie]

I am attempting to write a CustomGPT that will combine data from several sources, one of which is confluence.  

If I go to https://id.atlassian.com/manage-profile/security/api-tokens and generate a token without scopes, encode it with my username and use it in the request, it works fine, but if I try and limit the scopes in any way, it returns a 403.

I don't think the issue is the baseURL or pageID I'm providing because it works with an an unscoped token, but doesn't work with a scoped token

[marc -Collabello--Phase Locked-]

Scoped and unscoped tokens use different urls.  Unscoped use yourinstance.atlassian.net, and scoped use api.atlassian.com.

[Thiago P _Atlassian Support_]

Hey there @David Soucie ,

Complementing on what @marc -Collabello--Phase Locked- mentioned, the URL used for scoped API tokens is the following:

https://api.atlassian.com/ex/confluence/<cloud-id> --user user@domain.com:api-token

For further details, make sure to review Manage API tokens for your Atlassian account.

Hope this helps! =]