POST /v1/services/dashboardServices
Create a Dashboard Service
Create a new dashboard service connection
POST
POST /v1/services/dashboardServices
Documentation Index
Fetch the complete documentation index at: https://openmetadata-codex-audit-docs-codebase-alignment.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Create a Dashboard Service
Create a new dashboard service connection to a platform such as Superset, Looker, or Tableau.Body Parameters
Name of the dashboard service. Must be unique across all dashboard services.
Type of dashboard service (e.g.,
Superset, Looker, Tableau, Metabase, Redash, PowerBI, Mode, QlikSense, QlikCloud, Lightdash, DomoDashboard, CustomDashboard).Description of the dashboard service in Markdown format.
Human-readable display name for the dashboard service.
Connection configuration specific to the service type.
Array of owner references (users or teams) to assign to the service.
Fully qualified name of the domain to assign for governance purposes.
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
Unique identifier for the dashboard service (UUID format).
Dashboard service name.
Fully qualified name of the service.
Human-readable display name.
Description of the dashboard service in Markdown format.
Type of dashboard service (e.g., Superset, Looker, Tableau, Metabase, PowerBI).
Connection configuration for the service.
List of owners assigned to the dashboard service.
Fully qualified name of the assigned domain.
Classification tags applied to the dashboard service.
Version number for the entity (starts at 0.1).
Create or Update (PUT)
UsePUT /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.Bulk Create or Update (PUT)
UsePUT /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
| Code | Error Type | Description |
|---|---|---|
400 | BAD_REQUEST | Invalid request body or missing required fields |
401 | UNAUTHORIZED | Invalid or missing authentication token |
403 | FORBIDDEN | User lacks permission to create dashboard services |
409 | ENTITY_ALREADY_EXISTS | Dashboard service with same name already exists (POST only) |