Usage of personal API token with scopes

Question

I have created a personal 'API token with scopes' with the following scopes. read:issue:jira read:project:jira read:user:jira read:user.property:jira read:user-configuration:jira read:issue.watcher:jira write:issue:jira write:project:jira write:issue.watcher:jira export JIRA_EMAIL="" export JIRA_TOKEN="" export JIRA_SITE_SCOPED="api.atlassian.com/ex/jira/" With this curl command, I am getting error: "error":"Not Found","message":"No message available","path":"/ex/jira//rest/api/3/issue" Curl command : curl -v -u "$JIRA_EMAIL:$JIRA_TOKEN" \ -X POST \ -H "Content-Type: application/json" \ -H "Accept: application/json" \ "https://$JIRA_SITE_SCOPED/rest/api/3/issue" \ --data '{ "fields": { "project": { "key": "BSAC" }, "summary": "Sample issue created via curl", "description": { "type": "doc", "version": 1, "content": [ { "type": "paragraph", "content": [ { "type": "text", "text": "This issue was created using Jira REST API." } ] } ] }, "issuetype": { "name": "New Hire" } } }'

Mohamed Benziane · Accepted Answer

Hi, You need to pass your jira id and not the org id here : export JIRA_SITE_SCOPED="api.atlassian.com/ex/jira/" it should be https://api.atlassian.com/ex/jira//

Arkadiusz Wroblewski · Accepted Answer

Hello @Das Chebattina

As @Mohamed Benziane mentioned  that 404 Not Found almost always means the <cloud id> in the URL is not your Jira cloudId (people often paste an orgId / directoryId / something else).You want the ID that belongs to your Jira site (tenant), not your Atlassian org.

Have a great Day and soon Weekend 🤠☀️

Marc -Devoteam- · Accepted Answer

Hi @Das Chebattina

Use https://your-site-name.atlassian.net/_edge/tenant_info to get your Cloud ID

Das Chebattina_ibqmid · Accepted Answer

Thank you. Found that there was type in the Cloud Id. Corrected it and its working as expected.