Skip to main content
POST
POST /v1/dashboards

Create a Dashboard

Create a new dashboard within a dashboard service.

Body Parameters

string
required
Name of the dashboard. Must be unique within the parent dashboard service.
string
required
Fully qualified name of the parent DashboardService (e.g., sample_superset).
string
Human-readable display name for the dashboard.
string
Description of the dashboard in Markdown format.
string
URL of the dashboard in the source system.
array
Array of chart fully qualified names to associate with the dashboard.
array
Array of owner references (users or teams) to assign to the dashboard.
string
Fully qualified name of the domain to assign for governance purposes.
array
Array of classification tags to apply to the dashboard.
object
Custom property values defined by your organization’s metadata schema.
POST /v1/dashboards

Returns

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

Response

string
Unique identifier for the dashboard (UUID format).
string
Dashboard name.
string
Fully qualified name in format service.dashboardName.
string
Human-readable display name.
string
Description of the dashboard in Markdown format.
object
Reference to the parent dashboard service.
string
URL of the dashboard in the source system.
string
Type of dashboard service (e.g., Superset, Looker, Tableau, Metabase, PowerBI).
array
List of charts associated with the dashboard.
array
List of owners assigned to the dashboard.
array
Domain assignments for governance.
array
Classification tags applied to the dashboard.
object
Custom property values defined by your organization’s metadata schema.
number
Version number for the entity (starts at 0.1).

Create or Update (PUT)

Use PUT /v1/dashboards instead of POST to perform an upsert. If a dashboard with the same fullyQualifiedName already exists, it will be updated; otherwise, a new dashboard 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/dashboards/bulk to create or update multiple dashboards in a single request. The request body is an array of create request objects.

Error Handling