Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

403 Error from Node12 works in POSTMAN and CURL

Diego Link April 28, 2025

Calling basic the Get Issue API returns a 403. 

URL:

https://{myorg}.atlassian.net/rest/api/3/issue/{issue_id}

 

stopped working April 27, 2025 - from the server. No code changed.  This call works  just fine if I make the same call using curl  on the machine

 

Returns 403 error: Forbidden: Error

return axios({
method: options.method || 'GET',
headers: { Authorization: `Basic ${basicAuthToken}` },
url,
data,
}).then(res => res)
.catch(error => this.getJiraError(error));
}

 

Works fine from the same machine

curl --location 'https://{myorg}.atlassian.net/rest/api/3/issue/157159' --header 'Authorization: Basic {base64token'}

 

1 answer

0 votes
Diego Link May 5, 2025

Answering my own question for anyone who has to support legacy Node application making requests to atlassian apis.

My current theory is that Axios .26 is just not compatible at the protocol level. 

We changed it to fetch calls and it works fine:

 

 


FROM:

return axios({
method: options.method || 'GET',
headers: { Authorization: `Basic ${basicAuthToken}` },
url,
data,
}).then(res => res)

TO:

return fetch(url, reqOptions).then(res => res.json().then((result) => {
console.log('JIRA FETCH REQUEST RESULT', url, result);
return { data: result };
}))

 

 

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events