> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open-metadata.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a Dashboard Service

> Create a new dashboard service connection

# Create a Dashboard Service

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

## Body Parameters

<ParamField body="name" type="string" required>
  Name of the dashboard service. Must be unique across all dashboard services.
</ParamField>

<ParamField body="serviceType" type="string" required>
  Type of dashboard service (e.g., `Superset`, `Looker`, `Tableau`, `Metabase`, `Redash`, `PowerBI`, `Mode`, `QlikSense`, `QlikCloud`, `Lightdash`, `DomoDashboard`, `CustomDashboard`).
</ParamField>

<ParamField body="description" type="string">
  Description of the dashboard service in Markdown format.
</ParamField>

<ParamField body="displayName" type="string">
  Human-readable display name for the dashboard service.
</ParamField>

<ParamField body="connection" type="object">
  Connection configuration specific to the service type.

  <Expandable title="properties">
    <ParamField body="config" type="object">
      Service-specific connection configuration (e.g., hostPort, username, password for Superset).
    </ParamField>
  </Expandable>
</ParamField>

<ParamField body="owners" type="array">
  Array of owner references (users or teams) to assign to the service.

  <Expandable title="properties">
    <ParamField body="id" type="string">
      UUID of the owner entity.
    </ParamField>

    <ParamField body="type" type="string">
      Type of owner entity (e.g., `user`, `team`).
    </ParamField>

    <ParamField body="name" type="string">
      Name of the owner entity.
    </ParamField>
  </Expandable>
</ParamField>

<ParamField body="domain" type="string">
  Fully qualified name of the domain to assign for governance purposes.
</ParamField>

<ParamField body="tags" type="array">
  Array of classification tags to apply to the dashboard service.

  <Expandable title="properties">
    <ParamField body="tagFQN" type="string" required>
      Fully qualified name of the tag.
    </ParamField>

    <ParamField body="labelType" type="string">
      Type of label (e.g., `Manual`, `Derived`, `Propagated`).
    </ParamField>

    <ParamField body="state" type="string">
      State of the tag (e.g., `Suggested`, `Confirmed`).
    </ParamField>
  </Expandable>
</ParamField>

<RequestExample dropdown>
  ```python POST /v1/services/dashboardServices theme={null}
  from metadata.sdk import configure
  import requests

  configure(
      host="https://your-company.open-metadata.org/api",
      jwt_token="your-jwt-token"
  )

  # Direct API call for dashboard services
  response = requests.post(
      "https://your-company.open-metadata.org/api/v1/services/dashboardServices",
      headers={"Authorization": "Bearer your-jwt-token"},
      json={
          "name": "sample_looker",
          "displayName": "Sample Looker",
          "serviceType": "Looker",
          "description": "Production Looker instance",
          "connection": {
              "config": {
                  "type": "Looker",
                  "clientId": "your-client-id",
                  "clientSecret": "***",
                  "hostPort": "https://looker.example.com:443"
              }
          }
      }
  )

  service = response.json()
  print(f"Created: {service['fullyQualifiedName']}")
  ```

  ```java POST /v1/services/dashboardServices theme={null}
  import static org.openmetadata.sdk.fluent.DashboardServices.*;

  DashboardService service = DashboardServices.builder()
      .name("sample_looker")
      .serviceType("Looker")
      .connection(lookerConnection()
          .clientId("your-client-id")
          .clientSecret("***")
          .hostPort("https://looker.example.com:443"))
      .create();
  ```

  ```bash POST /v1/services/dashboardServices theme={null}
  curl -X POST "{base_url}/api/v1/services/dashboardServices" \
    -H "Authorization: Bearer {access_token}" \
    -H "Content-Type: application/json" \
    -d '{
      "name": "sample_looker",
      "serviceType": "Looker",
      "description": "Production Looker instance",
      "connection": {
        "config": {
          "type": "Looker",
          "clientId": "your-client-id",
          "clientSecret": "***",
          "hostPort": "https://looker.example.com:443"
        }
      }
    }'
  ```
</RequestExample>

<ResponseExample>
  ```json Response theme={null}
  {
    "id": "2c0c7c05-d820-4bea-a471-047deb7f92fd",
    "name": "sample_looker",
    "fullyQualifiedName": "sample_looker",
    "serviceType": "Looker",
    "description": "Production Looker instance",
    "version": 0.1,
    "updatedAt": 1769982621219,
    "updatedBy": "admin",
    "href": "http://localhost:8585/api/v1/services/dashboardServices/2c0c7c05-d820-4bea-a471-047deb7f92fd",
    "connection": {
      "config": {
        "type": "Looker",
        "clientId": "your-client-id",
        "clientSecret": "***",
        "hostPort": "https://looker.example.com:443"
      }
    },
    "owners": [],
    "tags": [],
    "deleted": false,
    "domains": []
  }
  ```
</ResponseExample>

***

## Returns

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

## Response

<ResponseField name="id" type="string">
  Unique identifier for the dashboard service (UUID format).
</ResponseField>

<ResponseField name="name" type="string">
  Dashboard service name.
</ResponseField>

<ResponseField name="fullyQualifiedName" type="string">
  Fully qualified name of the service.
</ResponseField>

<ResponseField name="displayName" type="string">
  Human-readable display name.
</ResponseField>

<ResponseField name="description" type="string">
  Description of the dashboard service in Markdown format.
</ResponseField>

<ResponseField name="serviceType" type="string">
  Type of dashboard service (e.g., Superset, Looker, Tableau, Metabase, PowerBI).
</ResponseField>

<ResponseField name="connection" type="object">
  Connection configuration for the service.

  <Expandable title="properties">
    <ResponseField name="config" type="object">
      Service-specific connection configuration.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="owners" type="array" optional>
  List of owners assigned to the dashboard service.

  <Expandable title="properties">
    <ResponseField name="id" type="string">
      UUID of the owner entity.
    </ResponseField>

    <ResponseField name="type" type="string">
      Type of owner entity (e.g., `user`, `team`).
    </ResponseField>

    <ResponseField name="name" type="string">
      Name of the owner entity.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="domain" type="string" optional>
  Fully qualified name of the assigned domain.
</ResponseField>

<ResponseField name="tags" type="array" optional>
  Classification tags applied to the dashboard service.

  <Expandable title="properties">
    <ResponseField name="tagFQN" type="string">
      Fully qualified name of the tag.
    </ResponseField>

    <ResponseField name="labelType" type="string">
      Type of label (e.g., `Manual`, `Derived`, `Propagated`).
    </ResponseField>

    <ResponseField name="state" type="string">
      State of the tag (e.g., `Suggested`, `Confirmed`).
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="version" type="number">
  Version number for the entity (starts at 0.1).
</ResponseField>

***

## 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`.

```bash theme={null}
curl -X PUT "{base_url}/api/v1/services/dashboardServices" \
  -H "Authorization: Bearer {access_token}" \
  -H "Content-Type: application/json" \
  -d '{ ... same body as POST ... }'
```

<Note>
  `PUT` will not return a `409` conflict error if the entity already exists -- it will update the existing entity instead.
</Note>

***

## 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.

```bash theme={null}
curl -X PUT "{base_url}/api/v1/services/dashboardServices/bulk" \
  -H "Authorization: Bearer {access_token}" \
  -H "Content-Type: application/json" \
  -d '[
    { "name": "service_one", "serviceType": "Superset", "connection": { "config": {} } },
    { "name": "service_two", "serviceType": "Looker", "connection": { "config": {} } }
  ]'
```

***

## 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) |