All entities in the GraphQL Gateway should be queried using their ARIs. An ARI is an Atlassian resource identifier that acts as one single entry point, and thus needs to have routing information to know which tenant to go to. Some common ARIs you may need are:
ari:cloud:beacon:{cloudId}:workspace/{workspaceId}
ari:cloud:beacon:{cloudId}:alert/{workspaceId}/{alertId}
Use the following table to learn the differences between your Atlassian IDs. This page also has instructions on how to assemble or retrieve your ARI.
ID type | Description | URL location |
---|---|---|
Org ID | The ID for your central place for managing your users and apps. This isn’t needed in the ARI, but you can use it to use GraphQL to build sections of your ARI. Example: | Look for the string after /o/ in your URL. |
Cloud ID | The ID for your specific Atlassian domain, such as Example: | Look for the string after /s/ in your URL. |
Workspace ID | The ID for a specific app instance, such as your Guard Detect workspace, or a Confluence site. Example: | Look for the string after /w/ in your URL. |
Alert ID | The ID for a specific alert within Guard Detect. Example: | Look for the string after /alerts/ in your URL. |
/o/
in your address bar./w/
in your address bar./s/
in your address bar./alerts/
in your address bar.Your alert ID is the most variable part of your ARI, and it’s easy to find from your alert in Guard Detect. Your workspace ID and cloud ID are more static, so you can use GraphQL to build these parts of your ARI, then manually add an individual alert ID to complete your ARI.
You can find your cloud ID through a GraphQL query. In the API explorer, paste this code into the main query window:
1 2query getCloudIdByActivationId($workspaceId: ID!) { tenantContexts(activationIds: [$workspaceId]) { cloudId __typename } }
Note that ActivationId
and workspaceId
refer to the same string.
Variables:
1 2{ "workspaceId": "your-workspace-id-here" }
Sample response:
1 2{ "tenantContexts": [ { "cloudId": "0626c985-4528-48ad-b462-55ef9ae78377", "__typename": "TenantContext" } ] }
You can use a query to return the Guard Detect workspace ARI. This contains your cloud ID and your workspace ID.
In the API explorer, paste this code into the main query window:
1 2query getWorkspaceByOrg($orgId: ID!) { shepherd { workspaceByOrgId(orgId: $orgId) { ari } } }
Variables:
1 2{ "orgId": "2949a768-1846-16jb-k194-88cd7jc56055" }
Sample response
1 2{ "data": { "shepherd": { "workspaceByOrgId": { "ari": "ari:cloud:beacon:0626c985-4528-48ad-b462-55ef9ae78377:workspace/6ab72b68-f091-4793-885a-2babf02aebf5" } } } }
To assemble your alert ARI, use the relevant cloud ID, workspace ID and alert ID with the following syntax:
1 2ari:cloud:beacon:<your-cloud-ID>:alert/<your-workspace-ID>/<an-alert-ID>
For example:
1 2ari:cloud:beacon:0626c985-4528-48ad-b462-55ef9ae78377:alert/67f42cd4f6e5bb72e88ae028/6ab72b68-f091-4793-885a-2babf02aebf5
Rate this page: