Authorization: Basic base64(email:api_token)). I have also ensured that the service account has proper project permissions like Browse Projects, Create Issues, Edit Issues, and Create Attachments, and it is added to the required groups/roles. Despite this, the APIs are still not working with the service account while they work fine with the personal account. I would like to understand if there are any differences in how service account API tokens work compared to user API tokens, if there are any additional configurations or limitations for service accounts in Jira Cloud, and whether there are any special requirements for using APIs like attachments with service accounts. Any guidance on this would be helpful as I want to use a service account instead of a personal account for automation purposes.Hello @Deepak Chawla
Test in this order:
GET https://api.atlassian.com/ex/jira/<cloudId>/rest/api/3/myself
GET https://api.atlassian.com/ex/jira/<cloudId>/rest/api/3/project/PROJECTKEY
GET https://api.atlassian.com/ex/jira/<cloudId>/rest/api/3/issue/ISSUEKEY
If those fail, the problem is still account access, token scopes, project permissions, or issue security.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.