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

# Describe Datasource

> Describe one datasource the way the report builder sees it: its data views (with the `advanced` keys each view requires), its default view and defaults, and its metric and dimension catalogs carrying the flags that decide what can be combined (`single` — must be the only dimension; `requires_metric` — only offered once that metric is picked; `deprecated`; `custom`). A metric or dimension is only valid inside its own `data_view`. Pass `data_view` to scope the response to one view.



## OpenAPI

````yaml https://api.oviond.com/openapi.json get /v1/data/{datasource_id}/describe
openapi: 3.1.0
info:
  title: Oviond Backend API
  version: 1.0.0
  description: Authentication, account management, billing, and media services for Oviond.
  x-logo:
    url: https://app.oviond.com/img/oviond-full-logo.svg
    altText: Oviond
servers:
  - url: https://api.oviond.com
    description: Production
security:
  - ApiKeyAuth: []
  - BearerAuth: []
paths:
  /v1/data/{datasource_id}/describe:
    get:
      tags:
        - Data
      summary: Describe Datasource
      description: >-
        Describe one datasource the way the report builder sees it: its data
        views (with the `advanced` keys each view requires), its default view
        and defaults, and its metric and dimension catalogs carrying the flags
        that decide what can be combined (`single` — must be the only dimension;
        `requires_metric` — only offered once that metric is picked;
        `deprecated`; `custom`). A metric or dimension is only valid inside its
        own `data_view`. Pass `data_view` to scope the response to one view.
      operationId: describe_datasource
      parameters:
        - schema:
            type: string
            example: gadw
          required: true
          name: datasource_id
          in: path
        - schema:
            type: string
            example: ACCOUNT
          required: false
          name: data_view
          in: query
      responses:
        '200':
          description: Data views, required advanced keys, and the field catalogs
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DataProxyResponse'
        '404':
          description: Unknown datasource
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: string
                required:
                  - error
components:
  schemas:
    DataProxyResponse:
      type: object
      properties:
        success:
          type: boolean
          enum:
            - true
        data: {}
        meta: {}
      required:
        - success
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      description: >-
        Oviond API key (prefix `oviond_`) sent as a Bearer token — the
        credential for REST/programmatic and headless integrations. Manage keys
        in Settings → API Keys. API keys do NOT authenticate the MCP endpoint
        (/mcp), which uses OAuth 2.1 + PKCE.
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        Supabase-issued JWT used by the Oviond web app session. External API
        consumers should authenticate with an Oviond API key (ApiKeyAuth)
        instead.

````