I want to read JIRA issue data with scoped token but getting 404

[Tomas Hajek _DHL IT Services_]

Hello colleagues,

I am using REST API v3 on Jira cloud platform.

endpoint: /rest/api/3/issue/{issueKey}

to authenticate, I generated two apikeys in my account:

key1: One non-scoped, full access

key2: scoped with read:jira-work (as per documentation in the API here: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-get )

I use Postman. I use basic authentication with username=my email, password=key1 or key2

When I use the full key1, I get the data.

When I use the scoped key2, I get 404 refusal.

I am digging through whole internet for few hours now and just cannot get what is wrong... Anybody got similar experience?

Thanks a lot!!

[Mikael Sandberg]

What domain are you using when accessing the endpoint? Scoped tokens have to use api.atlassian.com domain instead of yourdomain.atlassian.net, and for Jira the URL should look like this:

https://api.atlassian.com/ex/jira/<cloudid>/<api>

[Mikael Sandberg]

Btw, the documentation for it is under Service Accounts, but the scoped domains applies to any scoped API token, and you can find the documentation here.