Databricks

Collect cluster configuration, job, and workspace-user inventory as read-only compliance evidence through the Databricks REST API (self-hosted workspace). Substitute your workspace URL for the <your-workspace> placeholder in the base URL.

Connect Databricks All integrations

Data · Lakehouse

Tier 2 generic template — runs on the HTTP / REST endpoint connector

Evidence coverage

What this connector audits

Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.

Read-only API inventory endpoint checks
Evidence assets generated through the generic HTTP connector

Read-only calls

Endpoints this template queries

The exact Databricks API endpoints called once connected. All read-only GET requests unless noted.

GET/clusters/list
GET/jobs/list
GET/preview/scim/v2/Users

Least privilege

What we need

Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.

Required

Base URL(prefilled: https://<your-workspace>.cloud.databricks.com/api/2.0)
Endpoints (JSON)(prefilled: [ { "id": "clusters", "name": "Clusters", "path": "/clusters/list" }, { "id": "jobs", "name": "Jobs", "path": "/jobs/list" }, { "id": "scim-users", "name": "Workspace users (SCIM)", "path": "/preview/scim/v2/Users" } ])

Optional

Auth header name(prefilled: Authorization)
Auth header value(secret credential)

Where this evidence goes

Which frameworks this evidence supports

Databricks evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.

Don't see your system?

Tell us what you use and what it needs to prove. We'll follow up about adding a connector.

Wire in Databricks evidence

Get a guided demo, or start by scanning any domain for free.

Connect Databricks Browse all integrations