404 for REST api with App for Ticket and user management

Question

An app has been created to create, update and search issues and users all related Classic Scopes have been added for this but following response is received

{"timestamp":"2023-08-10T14:26:46.054447Z","status":404,"error":"Not Found","message":"No message available","path":"/ex/jira/47dfb529-5634-42c2-b86d-ac8be1d454f8/rest/api/2/issue/"}

The authentication URL contains all these scopes

read:me read:account read:jira-user read:jira-work manage:jira-project manage:jira-configuration write:jira-work manage:jira-webhook manage:jira-data-provider offline_access

404

Same in case of

POST /rest/api/2/issue

PUT /rest/api/2/issue/bulk

danish_kaleem · Answer

@Rudy Holtkamp  Thank you for the response. 
Actually I am using URL with app code, I did not included in here, the issue seems more like with app setting or some kind of permission because it works well with my other app which is in production. 
I have created another app and facing this issue here, while it is a exact copy of old one, when I use APPCODE of old app it works fine, when use with new APP CODE it throws 404 for all end points previous is working fine with my same development code.

Rudy Holtkamp · Answer

Hi @danish_kaleem ,

It seems that you don't use a valid REST endpoint.

Should: /ex/jira/47dfb529-5634-42c2-b86d-ac8be1d454f8/rest/api/2/issue/

Be something like: /ex/jira/47dfb529-5634-42c2-b86d-ac8be1d454f8/rest/api/2/issue/ABC-123

or /ex/jira/47dfb529-5634-42c2-b86d-ac8be1d454f8/rest/api/2/issue/12345

Where ABC-123 is a valid issue key and 12345 is a valid issue id.

You might did not wait on an async response which provided the key/id.