--- title: "List Databricks integration accounts" method: GET path: "/api/v2/integration-interfaces/databricks/accounts" tags: ["Databricks Integration"] --- # List Databricks integration accounts `GET /api/v2/integration-interfaces/databricks/accounts` ## Request - Base URL: `https://api.datadoghq.com` - URL: `https://api.datadoghq.com/api/v2/integration-interfaces/databricks/accounts` - Auth: one of: - API key in header `DD-API-KEY` and API key in header `DD-APPLICATION-KEY` - OAuth 2 - Authorization code: `/oauth2/v1/authorize` - Token URL: `/oauth2/v1/token` - TypeScript: (a function with typed inputs; its response is checked against the schema) List Databricks integration accounts. ## Response `200` OK - DatabricksIntegrationAccountsResponse: Response payload for a list of Databricks integration accounts. - `data` DatabricksIntegrationAccountResponseData[], required: List of Databricks integration accounts. - `attributes` DatabricksIntegrationAccountResponseAttributes, required: Attributes of a Databricks integration account returned in responses. - `authentication` union: Authentication configured on the Databricks integration account. A `bearer_token` method indicates an account still on token authentication, which Databricks accepts only on accounts that already use it. - DatabricksIntegrationAccountOAuthAuthResponse: The Databricks OAuth authentication method and service principal configured on the account. - `auth_type` 'databricks_oauth', required: The authentication method type. - `azure_tenant_id` string: Microsoft Entra ID tenant of the service principal, for Azure Databricks workspaces. - `client_id` string, required: Client ID of the Databricks service principal. - DatabricksIntegrationAccountPrivateActionRunnerAuthResponse: The Private Action Runner authentication method configured on the account. - `auth_type` 'private_action_runner', required: The authentication method type. - `connection_id` string, uuid, required: Unique identifier of the Private Action Runner connection holding the credentials. - `secret_path` string: Path of the credential inside the secret backend configured on the runner. - `user_uuid` string, uuid, required: Unique identifier of the user the Private Action Runner connection belongs to. - DatabricksIntegrationAccountBearerTokenAuthResponse: The bearer token authentication method configured on the account. - `auth_type` 'bearer_token', required: The authentication method type. - `dataflows` DatabricksIntegrationDataflowsResponse: Data Datadog collects from Databricks, keyed by dataflow id. - `databricks-cloud-cost-metrics` DatabricksCloudCostMetricsIntegrationDataflowResponse: Cost data collected from your Databricks system tables. Requires [Cloud Cost Management](https://docs.datadoghq.com/cloud_cost_management/) to be set up for your organization. - `enabled` boolean: Whether Datadog collects this data. - `settings` DatabricksCloudCostMetricsIntegrationDataflowSettingsResponse: Settings of the Cloud Cost Management dataflow. - `ccm_collect_all_workspaces` boolean: Whether cost data is collected for every workspace in the Databricks account rather than this workspace only. This takes effect across the Databricks account: if any one workspace enables it, Datadog collects cost data for all of them regardless of their individual settings, and every covered workspace incurs Cloud Cost Management charges. - `databricks-data-observability-jobs-monitoring` DatabricksDataObservabilityJobsMonitoringIntegrationDataflowResponse: Data Jobs Monitoring, which collects performance, reliability, and cost data for your Databricks jobs. - `enabled` boolean: Whether Datadog collects this data. - `settings` DatabricksDataObservabilityJobsMonitoringIntegrationDataflowSettingsResponse: Settings of the Data Jobs Monitoring dataflow. - `dd_api_key_id` string: ID of the Datadog API key the global init script uses to submit data. - `djm_global_init_script_enabled` boolean: Whether Datadog installs and manages the Agent on your Databricks clusters through a global init script. The script does not apply to clusters in Standard access mode. When `false`, the Agent is installed manually. - `script_gpum_enabled` boolean: Whether GPU metrics are collected from your Databricks clusters. The Agent installed by the global init script performs the collection, so this requires the dataflow to be enabled with `djm_global_init_script_enabled` set to `true`. - `script_logs_enabled` boolean: Whether driver and worker logs are collected from your Databricks clusters. The Agent installed by the global init script performs the collection, so this requires the dataflow to be enabled with `djm_global_init_script_enabled` set to `true`. - `serverless_jobs_enabled` boolean: Whether health and cost data is collected for jobs running on Serverless or SQL Warehouse compute. This compute has no clusters for the global init script to target, so collection reads the Databricks system tables and requires `system_tables_sql_warehouse_id`. - `databricks-data-observability-quality-monitoring` DatabricksDataObservabilityQualityMonitoringIntegrationDataflowResponse: Data Observability, which collects lineage and data quality information from your Databricks catalogs so you can explore how data flows and detect, resolve, and prevent quality issues. - `enabled` boolean: Whether Datadog collects this data. - `settings` DatabricksDataObservabilityQualityMonitoringIntegrationDataflowSettingsResponse: Settings of the Data Observability dataflow. - `do_crawlers_cron` string: Cron expression setting how often Datadog connects to your Databricks warehouse to collect metadata. Currently, only hourly (`0 * * * *`) and daily (`0 0 * * *`) are supported. - `sync_system_catalog` boolean: Whether metadata from the Databricks `system` catalog is included in Data Observability alongside your data catalogs. - `databricks-model-serving-metrics` DatabricksModelServingMetricsIntegrationDataflowResponse: Health and usage metrics for your Databricks model serving endpoints. Not supported on accounts that authenticate with `private_action_runner`; on those accounts this dataflow collects no data. - `enabled` boolean: Whether Datadog collects this data. - `name` string, required: Human-readable name of the Databricks integration account. - `settings` DatabricksIntegrationAccountSettingsResponse, required: Settings configured on the Databricks integration account. - `system_tables_sql_warehouse_id` string: ID of the SQL warehouse used to query the Databricks system tables. - `workspace_url` string, required: URL of the Databricks workspace. - `id` string, required: Server-generated unique identifier of the Databricks integration account. - `type` 'integration-account', required: The type of the integration account resource. Always `integration-account`. ## Other responses - `400`: Bad Request - `403`: Forbidden - `404`: Not Found - `429`: Too many requests --- [API](https://skmtc.dev/datadog/apis/datadog-api-v2-collection.md) - [All operations](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/llms.txt) - [OpenAPI document](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/revisions/3f70db624329?raw)