Issue Using Jira REST API -

Atlassian Developer Tools
1

Hi I am getting the following error… This has been working for months and all of a sudden is not working. We have not changed our Jira system. The user logged into the power Automate that is calling the reset api can login and can update the tickets in JIRA

I think your firewall is blocking our request.

https://.atlassian.net/rest/api/latest/issue/BIL-4252

{
“statusCode”: 404,
“headers”: {
“Transfer-Encoding”: “chunked”,
“Connection”: “keep-alive”,
“Date”: “Tue, 22 Jul 2025 12:40:19 GMT”,
“Server”: “AtlassianEdge”,
“Timing-Allow-Origin”: “*”,
“X-Arequestid”: “b62d4fc91c54e50753a1b7dfd6374e1c”,
“X-Seraph-Loginreason”: “AUTHENTICATED_FAILED”,
“Set-Cookie”: “atlassian.xsrf.token=4a6bd29c393cbe2f971eacf5fbc877eced7ab008_lout; Path=/; SameSite=None; Secure”,
“Cache-Control”: “no-store, no-transform, no-cache”,
“X-Content-Type-Options”: “nosniff”,
“X-XSS-Protection”: “1; mode=block”,
“Atl-Traceid”: “413edb5b73964ebab089d1495cfe49d2”,
“Atl-Request-Id”: “413edb5b-7396-4eba-b089-d1495cfe49d2”,
“Strict-Transport-Security”: “max-age=63072000; includeSubDomains; preload”,
“Report-To”: “{"endpoints": [{"url": "https://dz8aopenkvv6s.cloudfront.net"}], "group": "endpoint-1", "include_subdomains": true, "max_age": 600}”,
“Nel”: “{"failure_fraction": 0.001, "include_subdomains": true, "max_age": 600, "report_to": "endpoint-1"}”,
“Server-Timing”: “atl-edge;dur=120,atl-edge-internal;dur=21,atl-edge-upstream;dur=98,atl-edge-pop;desc="aws-eu-west-1"”,
“X-Cache”: “Error from cloudfront”,
“Via”: “1.1 f6b9514ab9239076a9af0bb69d273eb8.cloudfront.net (CloudFront)”,
“X-Amz-Cf-Pop”: “AMS58-P2”,
“X-Amz-Cf-Id”: “zUIhTlHF53gr-pfQyrz6icmUZIHcQkVlnFoRCHTH0SCEZjFgOUKJ9Q==”,
“Content-Type”: “application/json; charset=UTF-8”,
“Content-Length”: “95”
},
“body”: {
“errorMessages”: [
“Issue does not exist or you do not have permission to see it.”
],
“errors”: {}
}
}

2

Hello @siobhanMcLelland

That’s an invalid domain name. There needs to be something before the .atlassian.net part of the URL

Also, you said:

The user logged into the power Automate that is calling the reset api can login and can update the tickets in JIRA

Being able to login to Jira does not mean the user can access the REST API using either OAuth or Basic auth, both of which use tokens that either:

  1. Automatically expire due to a repeating time limit and must be renewed, or
  2. Can be preset to expire at a specific date when they are first created.

If the user’s API token has expired or is otherwise no longer valid, then the REST API will respond with an Unauthorised error.

3

Hey @siobhanMcLelland,

It looks like you’re accessing the get issue API for a cloud site.

The request isn’t being blocked, it’s returning a 404 error which indicates:

“404
Not Found
Returned if the issue is not found or the user does not have permission to view it.”

As @anon96974232 suggested, this could be due to a couple of reasons, I would check

  • Is the user whose API token is being used to access the API able to access BIL-4252 via the product UI?
  • Can they log into their Atlassian Account, then go to the security tab and review the list of API tokens to check the token has not expired (or been revoked).

Please do let me know if this helped you work out the cause of the error.

If you are still stuck, please confirm you are sending a GET request to the REST API, or trying to do something else.

Cheers!
Mel

4

Thank you both for responding

I generating a new API, which is working. Checked and tested all permissions.

The issue is the API call is no longer working. I’ve tested this in Postman. I can run a Get for the ticket URI, it works. However, when I change it to the Rest API call , it fails every time.

5

Excellent. Now that you’ve used Postman to confirm there’s no fault with the API token, and that token’s permissions work making a GET call to that API endpoint, it’s reasonable to assume you have a fault somewhere in your Power Automate workflow. You’ll need to systematically debug your workflow and find out where it’s going wrong and why.

Personally, I’ve not used Power Automate in more than a decade, and it’s not a topic that gets discussed on this forum, so you may not get any particularly specific advice here to resolve your problem.

Maybe visit some of the Microsoft Power Automate community forums and ask if someone is familiar with debugging auth issues with REST API calls?

Have fun.