Aliases

Aliases connect catalog entities to their corresponding resources in external systems. Alias types become available in your catalog entity type settings when you enable a connection to a third-party service in Admin > Connections. Once enabled, DX will automatically assign aliases when the name or identifier matches exactly.

Some alias types are multi-instance, meaning the same external system can be connected to DX more than once (for example, two separate Jira instances). For these alias types, the same identifier value may exist across multiple instances, and an instance_identifier can be paired with identifier to ensure the alias is linked to the correct instance.

For aliases that support URLs, the alias is linked back to the resource in the third-party system from within Software catalog.

Supported alias types

Alias type key: ado_repository
Database table: ado_repositories
Supports URLs: Yes

Alias type key: backstage_component
Database table: backstage_catalog_entities

Alias type key: bitbucket_server_repository
Database table: bitbucket_server_repositories
Supports URLs: Yes

Alias type key: bitbucket_repository
Database table: bitbucket_repositories
Supports URLs: Yes

Alias type key: bugsnag_project
Database table: bugsnag_projects

Alias type key: checkmarx_project
Database table: checkmarx_projects
Supports URLs: Yes

Alias type key: datadog_monitor
Database table: datadog_monitors

Alias type key: datadog_slo
Database table: datadog_slo_tags

Alias type key: datadog_service
Database table: datadog_services

Alias type key: dx_deployment_service
Database table: deployment_services

Alias type key: dx_incident_service
Database table: incident_services

Alias type key: dynatrace_entity
Database table: dynatrace_entities

Alias type key: dynatrace_slo
Database table: dynatrace_slos

Alias type key: firehydrant_service
Database table: firehydrant_services

Alias type key: github_repo
Database table: github_repositories
Supports URLs: Yes

Alias type key: gitlab_repo
Database table: gitlab_projects
Supports URLs: Yes

Alias type key: harness_project
Database table: harness_projects

Alias type key: incident_io_service
Database table: incident_io_services

Alias type key: jira_project
Database table: jira_projects
Supports URLs: Yes
Multi-instance: Yes

This alias type supports multiple connected Jira instances. Use the instance_identifier field alongside identifier to target a specific instance.

Instance identifier field Available values
jira_projects.jira_instance_id jira_instances

Alias type key: jsm_services
Database table: jsm_services

Alias type key: launchdarkly_project
Database table: launchdarkly_projects

Alias type key: linear_team
Database table: linear_teams
Supports URLs: Yes

Alias type key: newrelic_entity
Database table: newrelic_entities

Alias type key: opsgenie_service
Database table: opsgenie_services

Alias type key: pagerduty_service
Database table: pagerduty_services

Alias type key: rollbar_project
Database table: rollbar_projects

Alias type key: rootly_services
Database table: rootly_services

Alias type key: sentry_project
Database table: sentry_projects

Alias type key: servicenow_services
Database table: servicenow_services

Alias type key: snyk_project
Database table: snyk_projects

Alias type key: sonarcloud_project
Database table: sonarcloud_projects

Alias type key: sonarqube_project
Database table: sonarqube_projects

Alias type key: wiz_cloud_resource
Database table: wiz_cloud_resources

Using the API

Aliases are organized by alias type, with each type containing a list of alias entry definitions. The key in the object is the alias type. Each alias entry must include either identifier (optionally paired with instance_identifier for multi-instance alias types) or lookup, but not both.

To remove an alias, update or upsert a catalog entity with the alias type set to an empty array []. Omitted alias types are not affected.

Example Request

When creating or updating aliases, use identifier when you know the external system’s unique identifier for the alias entry. For multi-instance alias types, you can optionally include instance_identifier alongside identifier to target a specific connected instance.

Use lookup when you want the API to find a single matching alias entry by name or identifier from the Data Cloud database. A lookup value uses case-insensitive partial matching. If the lookup matches more than one alias entry, the request returns alias_lookup_ambiguous.

{
  "github_repo": [
    {
      "lookup": "get-dx/payment-processing"
    }
  ],
  "pagerduty_service": [
    {
      "identifier": "P123ABC"
    }
  ],
  "jira_project": [
    {
      "identifier": "PLAT",
      "instance_identifier": "abc123"
    }
  ]
}

Example Response

The API response will include the name and optional url fields that were fetched from the Data Cloud database:

{
  "github_repo": [
    {
      "identifier": "671150935",
      "name": "get-dx/payment-processing",
      "url": "https://github.com/get-dx/payment-processing"
    }
  ],
  "pagerduty_service": [
    {
      "identifier": "P123ABC",
      "name": "Payment Service"
    }
  ],
  "jira_project": [
    {
      "identifier": "PLAT",
      "instance_identifier": "1",
      "name": "Platform",
      "url": "https://your-org.atlassian.net/jira/software/projects/PLAT"
    }
  ]
}

Properties

Key Type Description
identifier string The external system’s unique identifier for the item. Required when lookup is not provided.
instance_identifier string For multi-instance alias types, identifies which connected instance the alias entry belongs to. Pair with identifier to ensure specificity.
lookup string A name or identifier fragment used to resolve one matching alias entry from Data Cloud. Required when identifier is not provided.
name string The display name of the item in the system. Returned in API responses, not required in requests.
url string When supported by the alias type, this will be a link to the item in the third-party system. Returned in API responses, not required in requests.