The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Testing REST connection to private JSM cloud instance gives 403 forbidden

Johannes Dickas
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!
November 21, 2025

I tried to connect to my private JSM instance with postman as it is described in your docs: https://docs.opsgenie.com/docs/account-api

The API-key I provided as header parameter.

I started with “Get Account Info”  GET request:

URL: https://api.opsgenie.com/v2/account

 

As response I got an 403 forbidden error:

The response body was:

{

    "code": 40301,

    "message": "Account is consolidated.",

    "took": 0.007,

    "requestId": "cd369203-0254-47b0-8fb0-f2d8fdb4a590"

}

 

For our companies OpsGenie instance this "Get Account Info" GET request works with a valid (Response Code 200) response

Can someone tell me, why this OpsGenie documented GET is not working with JSM?

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

5 votes
Answer accepted
Alexander Nilsson
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
November 21, 2025

Hello Johannes, 

for JSM-integrated Opsgenie instances, the legacy Account API endpoint `GET https://api.opsgenie.com/v2/account` is intentionally blocked and returns: { "code": 40301, "message": "Account is consolidated." }

This happens because the Opsgenie account is now managed under your Atlassian/Jira Service Management subscription, so the standalone Opsgenie Account API is not supported anymore for that site. The same call still works on our standalone Opsgenie tenant, which is why you get a 200 there.

For JSM-based Opsgenie (Operations), you need to use the supported JSM Operations APIs and Atlassian Cloud admin interfaces instead of `/v2/account`, depending on what data you actually need (alerts, schedules, integrations, etc.): https://developer.atlassian.com/cloud/jira/service-desk-ops/rest/v2/intro/

Greetings,

Alex

Johannes Dickas
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!
November 21, 2025

Thanks Alex

Like Alexander Nilsson likes this
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events