Testing REST connection to private JSM cloud instance gives 403 forbidden

[Johannes Dickas]

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?

[Alexander Nilsson · Accepted solution]

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]

Thanks Alex