Compass API suitable for operations after Opsgenie migration

Compass
1

Am I going crazy, or do these APIs just not exist: https://developer.atlassian.com/cloud/compass/rest/v1/api-group-alerts/#api-v1-alerts-get

I’m going through the migration process from OpsGenie to compass, and it’s pretty weird to be honest.

One of the steps after compass has turned on (with the one week waiting period, I assume someone doing some manual work in the background), we’re greeted with this “Compelte Opsgenie migration” button thing. One of the steps says to migrate to the APIs mentioned above. Trying all the examples, all I get are 404s.

Yes, using the basic auth - exactly the same syntax as what the curl examples provide. username is my email I use to login with atlassian, password is the API key generated from Atlassian account

example:

export AT_EMAIL="<my email>"
export AT_TOKEN="<token from API token generator page>"
export AT_CLOUDID="<cloud id>"

curl --request GET \                                    
  --url "https://api.atlassian.com/compass/cloud/${AT_CLOUDID}/ops/v1/alerts" \
  --user "${AT_EMAIL}:${AT_TOKEN}" \
  --header 'Accept: application/json'

Response:

{"timestamp":"2025-08-05T12:07:03.754672379Z","status":404,"error":"Not Found","message":"No message available","path":"/compass/cloud/<cloud id from above>/ops/v1/alerts"}

Also just checked loading this URL in a browser where I was logged into atlassian, and got a 404 too. What’s going on?

2

Pretty sure this is also breaking the Terraform provider.

resource "atlassian-operations_team" "testing" {
  description  = "Testing description"
  display_name = "Testing"
  member = [
    {
      account_id = "<accountid>"
    }
  ]
  organization_id = "<cloudid>"
  team_type       = "MEMBER_INVITE"
}

error:

atlassian-operations_team.testing: Creating...
╷
│ Error: Client Error
│ 
│   with atlassian-operations_team.testing,
│   on main.tf line 1, in resource "atlassian-operations_team" "testing":
│    1: resource "atlassian-operations_team" "testing" {
│ 
│ Unable to enable Operations for the created team, status code: 404. Got response:
│ {"timestamp":"2025-08-05T12:12:27.563237079Z","status":404,"error":"Not Found","message":"No message
│ available","path":"/compass/cloud/<cloudid>/ops/v1/teams/ec9fe322-6f97-4f78-8701-ae23ebd62cbe/enable-ops"}
╵

Checked the trace logs, it is calling: https://api.atlassian.com/compass/cloud/<cloudid>/ops/v1/teams/39773ec1-d938-4e0d-9522-42aea22c2f7f/enable-ops

This was after figuring out that I needed both the API tokens from different places in the Atlassian UIs.

Is compass half cooked?

3

I think this fixes it: Unable to Create Atlassian API Integration – 404 Not Found Error · Issue #66 · atlassian/terraform-provider-atlassian-operations · GitHub

The cloud id I was using was the organization id. Why? Because no where in any of the documentation is it clear what the hell id to use anywhere. Maybe it would be nice to include something in the API docs about what ID is what, and how to retrieve them. Better yet, don’t expose poor implementations to your customers.

I hope this saves someone else in the future the hours I lost trying to figure this out today.

1 Like