Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

v2/alerts/requests/ returning 404

Joel Bradley December 29, 2021


So recently my requests sent to are returning 404 errors.

If I don't include the authorization header I get could not authenticate, requests I send to work fine, and it worked okay last week.

No valid request id is working.

var uri = $"{requestId}";
client.Headers.Add(HttpRequestHeader.Authorization, genieKey);
request = client.DownloadString(uri);

I'm not sure what I'm doing wrong.

1 answer

0 votes
Connor Eyles
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 30, 2021

Hi @Joel Bradley 

Thanks for reaching out!

So in relation to this REST call

The Get Request Status endpoint is used to track the status and alert details (if any) of the request whose identifier is given.

I would like to point out I am not a C# specialist but in best efforts provide some information that may help you with your troubleshooting here. What I can do is share an example for this request using C# - RestSharp

using RestSharp;

using RestSharp.Authenticators;

var client = new RestClient("");

client.Timeout = -1;

var request = new RestRequest(Method.GET);

request.AddHeader("Authorization", "GenieKey eb243592-faa2-4ba2-a551q-1afdf565c889");

IRestResponse response = client.Execute(request);


Something I have noticed from your code is that your genieKey is not enclosed with "" like it is in my example code. You could try that and see if it works on your end!

Let me know how you go with this one or have any follow up questions.



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events