Skip to main content
POST
POST /v1/services/dashboardServices

Create a Dashboard Service

Create a new dashboard service connection to a platform such as Superset, Looker, or Tableau.

Body Parameters

string
required
Name of the dashboard service. Must be unique across all dashboard services.
string
required
Type of dashboard service (e.g., Superset, Looker, Tableau, Metabase, Redash, PowerBI, Mode, QlikSense, QlikCloud, Lightdash, DomoDashboard, CustomDashboard).
string
Description of the dashboard service in Markdown format.
string
Human-readable display name for the dashboard service.
object
Connection configuration specific to the service type.
array
Array of owner references (users or teams) to assign to the service.
string
Fully qualified name of the domain to assign for governance purposes.
array
Array of classification tags to apply to the dashboard service.
POST /v1/services/dashboardServices

Returns

Returns the created dashboard service object with all specified properties and system-generated fields.

Response

string
Unique identifier for the dashboard service (UUID format).
string
Dashboard service name.
string
Fully qualified name of the service.
string
Human-readable display name.
string
Description of the dashboard service in Markdown format.
string
Type of dashboard service (e.g., Superset, Looker, Tableau, Metabase, PowerBI).
object
Connection configuration for the service.
array
List of owners assigned to the dashboard service.
string
Fully qualified name of the assigned domain.
array
Classification tags applied to the dashboard service.
number
Version number for the entity (starts at 0.1).

Create or Update (PUT)

Use PUT /v1/services/dashboardServices instead of POST to perform an upsert. If a dashboard service with the same fullyQualifiedName already exists, it will be updated; otherwise, a new service is created. The request body is the same as POST.
PUT will not return a 409 conflict error if the entity already exists — it will update the existing entity instead. However, for certain fields (such as description, tags, owners, and custom properties), PUT preserves an already-populated value instead of overwriting it with an empty or omitted one — the exact behavior depends on the field and the calling user or bot’s permissions, not a blanket rule. See Entity Update Behavior for the full preserve/merge rules. Use PATCH to intentionally replace an existing value.

Bulk Create or Update (PUT)

Use PUT /v1/services/dashboardServices/bulk to create or update multiple dashboard services in a single request. The request body is an array of create request objects.

Error Handling