Forums

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

error-page error404 when trying to create jira issue using REST API

anil cheepuru December 17, 2018

Hi,

My inputs are as follows:

> URL used in Postman: http://localhost:8080/rest/api/3/issue 

> Added JSESSIONID and it's value in Cookie in Headers

> Request used:

{

  "fields": {

       "project":

       {

          "key": "FIRSTPRO"

       },

       "summary": "No REST for the Wicked.",

       "description": "Creating of an issue",

       "issuetype": {

          "name": "Bug"

       }

   }

}

> And I am getting below error in response xml:

<body class=" error-page error404">

I tried searching for solution in this community but I couldn't find one. Can anyone please help me with solution on this.

1 answer

1 accepted

0 votes
Answer accepted
Aleksandr Zuevich
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 18, 2018
anil cheepuru December 18, 2018

Hey,

Thanks for the response.

I have gone through your link. I have already performed cookie based authentication by generating JSESSIONID using my credentials. But when I was trying to create an issue, I got 404 not found error. Please let me know if you have more information on this.

Aleksandr Zuevich
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 18, 2018

There is 3 in your URL: http://localhost:8080/rest/api/3/issue but as I know the current API version is 2.
So you can use 2 or latest, i.e. http://localhost:8080/rest/api/2/issue or http://localhost:8080/rest/api/latest/issue 

Like anil cheepuru likes this
anil cheepuru December 18, 2018

neither of the two urls is not working. I am getting the error: Unauthorized (401). 

Do you have any other solution?

Aleksandr Zuevich
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 19, 2018

It seems that now you have correct URL but your auth method isn't correctly implemented. Maybe JSESSIONID cookie isn't enough. Try to use basic authentication or OAuth with the latest URL.

anil cheepuru December 19, 2018

Hey,

It is quite strange that the url you gave in your 2nd reply (http://localhost:8080/rest/api/2/issue) is working today; which wasn't yesterday. Not sure about the root cause of it though.

Since it is working fine as per your suggestion, I am accepting your answer.

Thanks a lot.

Suvarna Vashistha June 15, 2020

I am also facing same problem but neither of the URLs are working. Please suggest what else I could do? 

I have also performed cookie based authentication by generating JSESSIONID using my credentials. But same error is occurring in POSTMAN 404 not found

Taha Zahid
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 18, 2021

There is in your URL: http://localhost:8080/rest/api/3/issue but as I know the current API version is 2.
So you can use 2 or latest, i.e. http://localhost:8080/rest/api/2/issue or http://localhost:8080/rest/api/latest/issue 

#Copied

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events