databricks

Claim Partner Connect Provision

Changed on

Finish a Partner Connect setup started from the Databricks UI.

Databricks provisions against a workspace and has no idea which Qualia organization it belongs to, so the payload waits under a one-time token until an admin claims it here, where the organization is known.

post/api/databricks/claim-provision

Request

  • Base URL
    https://api.quadrillion.io (the document declares no server; this is the origin it was published from)
  • URL
    https://api.quadrillion.io/api/databricks/claim-provision
  • Auth
    none declared

Request body

tokenstring required

Response

Successful Response

configuredboolean required
workspace_hoststring nullable
workspace_idstring nullable
cloudstring nullable
oauth_client_idstring nullable
oauth_redirect_uristring nullable
has_client_secretboolean
enabled_auth_modesstring[]
service_principal_client_idstring nullable
federation_audiencestring nullable
federation_readyboolean
warehouse_idstring nullable
genie_agent_idstring nullable
default_catalogstring nullable
default_schemastring nullable
disabledboolean

Changes

  • abf76937a751Revision changes
    • info

      added the optional property // to the response with the status

    • info

      added the optional property // to the response with the status

  • dcf9b4550387Revision changes
    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status