REST API v3 "Get item" Curl Call Does Not Return Results

While working with the Get item REST API call using curl, getting the following response for items I can work with via the standard Jira Cloud web interface. It feels like I’m missing something basic, and any assistance would be greatly appreciated.

{"errorMessages":["Issue does not exist or you do not have permission to see it."],"errors":{}}

I believe to have successfully created a “classic” API token following the provided documentation. Using the same curl call to the “Server info” endpoint returns JSON similar to the example in the documentation.

{"baseUrl":"https://my-company-name.atlassian.net","displayUrl":"https://my-company-name.atlassian.net","displayUrlServicedeskHelpCenter":"https://my-company-name.atlassian.net","displayUrlCSMHelpSeeker":"https://my-company-name.atlassian.net","displayUrlConfluence":"https://my-company-name.atlassian.net","version":"1001.0.0-SNAPSHOT","versionNumbers":[1001,0,0],"deploymentType":"Cloud","buildNumber":100295,"buildDate":"2026-11-09T03:57:02.000-0500","scmInfo":"37bdb440188c5b94db5486d134b4d3bbf7517e25","serverTitle":"Jira","defaultLocale":{"locale":"en_US"},"serverTimeZone":"Etc/UTC"}

Lastly, snippet of the curl calls being made from a prototype bash script:

curl -D-
-u ${JIRA_EMAIL}:${JIRA_TOKEN2}
-X GET
-H ‘Accept: application/json’
“$JIRA_BASE_URL/rest/api/3/issue/$WORK_ITEM”

curl -D-
-u ${JIRA_EMAIL}:${JIRA_TOKEN2}
-X GET
-H ‘Accept: application/json’
“$JIRA_BASE_URL/rest/api/3/serverInfo”

Hi @Steven1,

The serverInfo 200 doesn’t mean the login works. That endpoint answers anonymously. A refused credential gets exactly your 404 body, and I got it with no auth, a wrong token, the wrong email and a trailing carriage return.

Your -D- headers tell you more. X-Seraph-LoginReason: AUTHENTICATED_FAILED on the 404 means the credential was sent and refused, while AUTHENTICATION_DENIED is the CAPTCHA case in the basic auth doc.

Then try /myself:

curl -sS -D- -u "${JIRA_EMAIL}:${JIRA_TOKEN2}" -H 'Accept: application/json' "$JIRA_BASE_URL/rest/api/3/myself"

A 401 is a bad pair. The usual suspects are an email from another account than the token’s, an expired token, an empty variable or a stray \r. A token created with scopes only works through the cloudId gateway in the token docs.

User JSON back means auth is fine. Then it’s the account or the key, since a missing key gets the same 404.

What does /myself return?

Thanks much! Tried the myself endpoint as suggested, and received a 401 response. While making changes to use a new API token, noticed a typo in the associated email. :person_facepalming: Corrected the email typo and got valid JSON returned.

Thanks again.