OpsGenie API api.eu.opsgenie.com/v2/alerts/requests/:requestId 403

Rasmus Glintborg Larsen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 18, 2025

Hello.

I am having issues giving permissions to an integration.

I can create alerts, and i can close alerts, but i get a 403 on the api.eu.opsgenie.com/v2/alerts/requests/:requestId endpoint - I have looked everywhere in OpsGenie, and i cannot figure out how to give permission to this endpoint.

 

This is the body i get back from the status 403 call.

 

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML>

<HEAD>
    <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
    <TITLE>ERROR: The request could not be satisfied</TITLE>
</HEAD>

<BODY>
    <H1>403 ERROR</H1>
    <H2>The request could not be satisfied.</H2>
    <HR noshade size="1px">
    Bad request.
    We can't connect to the server for this app or website at this time. There might be too much traffic or a
    configuration error. Try again later, or contact the app or website owner.
    <BR clear="all">
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
    <BR clear="all">
    <HR noshade size="1px">
    <PRE>
Generated by cloudfront (CloudFront)
Request ID: rXXFlH1lVE2eOojieUwSWWkASIcBqSbFzKsXrWfsNsYRrWidTO2oTg==
</PRE>
    <ADDRESS>
    </ADDRESS>
</BODY>

</HTML>

1 answer

1 accepted

2 votes
Answer accepted
Rasmus Glintborg Larsen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 18, 2025

All right, this was 100% on me.

I duplicated the working POST request in Postman and changed it to a GET and fixed the url etc but i never removed the body on the new GET request.

I got too hung up on the error message, about configuration error, or too much traffic alongside the status 403, I didn't notice the "Bad request" above it.

 

Hopefully this answer saves someone else an hour or two :)

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events