Create Databricks Connector
Body
POST /v1/connector -- Databricks credential variant.
The (server_hostname, http_path, catalog, schema_name)
tuple is the probe target: the server runs SELECT 1 against it
with the request's credentials. The credential row is only inserted
if the probe succeeds, and the tuple is stored on the row.
Unique-per-user name for this credential entry.
Databricks personal access token.
Databricks workspace hostname.
HTTP path of the SQL warehouse or cluster.
"databricks"Unity Catalog name; optional.
Schema within the catalog; optional.
Response
Successful Response
Returned by POST / GET endpoints.
The verified_* fields surface the probe target the credential
was validated against at create time. Exactly one set of fields is
populated per response, matching connector_type:
s3→verified_bucket_uri+verified_role_arn+verified_bucket_owner_account_idsnowflake→verified_account+verified_warehouse+verified_database+verified_schema_namedatabricks→verified_server_hostname+verified_http_pathverified_catalog+verified_schema_name
id is the stored credential's identifier — the value referenced as
connector_credential_id on a connection config and as connector_id
in the per-type delete route (DELETE /connectors/{type}/{connector_id}).
Supported external data source types for user-owned credentials.
s3, snowflake, databricks, file_upload