Forums

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

Jira Forms Rest API Keeps Giving 404 Response for Unknown Reason

Tony B
Contributor
February 21, 2025

I am using the Jira Forms Rest API and trying to access forms on an issue in a Jira Service Management project.

I know the issue exists. I know I have permission to view and edit the issue. I'm the administrator for the project, and I am looking at the issue right now.

I am able to read and write to that issue using the Atlassian jira python package, so I know my API token has sufficient permissions.

Can someone please help me figure out why I keep getting the 404 response? Here is my request (some info edited for privacy of course). This is me making a request to the "Get Form Index" endpoint. I'm using the documentation here:

https://developer.atlassian.com/cloud/forms/rest/api-group-forms-on-issue/#api-issue-issueidorkey-form-get

 

 

url = 'https://api.atlassian.com/jira/forms/cloud/xxx-mycloudid-xxx/issue/ABC-25/form'
auth = HTTPBasicAuth('myemail@mydomain.com', 'longAPITOKENstring')
headers = {"Accept" : "application/json",}
res = requests.get(url, auth=auth, headers=headers)
The response comes back with this message: 

'{"errors":[{"status":404,"code":"ISSUE_NOT_FOUND","title":"Issue Not Found","detail":"You do not have permission to access this resource, or it was not found.","context":[{"type":"issue","id":"ABC-25"}]}]}'

Has anyone EVER successfully used any endpoint of the Jira Forms Rest API? Any help would be greatly appreciated!

1 answer

1 accepted

7 votes
Answer accepted
Jehan Bhathena
Community Champion
February 21, 2025

Hi @Tony B ,

image.png

Works fine at my end.

Steps I would recommend:

* Verify your cloud ID using the API mentioned here:  https://developer.atlassian.com/cloud/forms/rest/intro#using-basic-auth

* Check if the Issue actually has a Form (via the UI)

* Verify your auth token (although you did received a 404 so the Auth might not be the problem here)

Let us know how it goes :-)

Tony B
Contributor
February 23, 2025

My goodness it was the cloud id! I foolishly just used the generic cloud id from the example URL and never even set my actual company domain *facepalm.

 

Thanks very much for your quick answer on this! A much needed sanity check :)

Like # people like this

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