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

# Get the tenant insight snapshot

> Requires an authenticated tenant session (any permission). Returns one coherent, versioned snapshot: the newest (dataset_version, model_version) pair with at least one `client_visible` collection, and every one of the nine client-facing insight collections at that pair (the tenth, `cause_remediation`, is export-only and withheld from this response). Each collection reports `ready` (payload present), `generating` (materialization pending), or `disabled` (an LLM-derived collection with no LLM configured for the tenant). Onboarding-era rows only appear if the tenant's `share_onboarding_outputs` flag is on; post-go-live ingest rows are always visible regardless of that flag.



## OpenAPI

````yaml /api-reference/openapi.json get /insights/snapshot
openapi: 3.1.0
info:
  title: CL MVP Product API
  description: >-
    The Causeloop MVP Product API is a deliberately small, explicitly
    allowlisted HTTP surface: `services/api/product_app.py` enumerates every one
    of the 44 published (method, path) operations drawn from seven routers, and
    only those operations are mounted onto this app -- everything else defined
    in the underlying routers (and the entire legacy research surface in
    `services/api/main.py`) is not exposed here. Staff (employee) and
    tenant-user sessions are separate cookie-based principals with no shared
    session table; mutating requests are protected by a double-submit CSRF
    cookie/header pair. See `/api-reference/authentication` for session and CSRF
    details, and `/api-reference/errors-and-conventions` for shared error shapes
    and status-code conventions.
  version: 1.0.0
servers: []
security: []
tags:
  - name: Auth
    description: >-
      Staff (employee) and tenant-user session lifecycle: login/logout,
      current-identity reads, invitation acceptance, and the public pre-login
      workspace directory.
  - name: Staff Onboarding
    description: >-
      The Onboarding Portal surface used to create, provision, ingest data for,
      train, activate, and go-live a tenant. Every operation requires an
      authenticated employee session; mutations additionally require the
      `onboarding_admin` control role (`support_readonly` employees can read but
      not write).
  - name: Insights
    description: >-
      Tenant-facing reads of materialized insight collections (themes, severity,
      issues, fishbone, and related model outputs) produced by the training and
      materialization pipeline.
  - name: Members
    description: Read-only tenant member directory.
  - name: Sources
    description: Tenant-facing source-connector registration and file-upload ingest.
  - name: Remediation
    description: >-
      Tenant-scoped corrective action plans (CAPs), human-in-the-loop issue
      reviews, the tenant audit trail, and the branded Excel export.
  - name: Health & Observability
    description: >-
      Unauthenticated liveness/readiness probes and the employee-only Prometheus
      metrics scrape endpoint.
paths:
  /insights/snapshot:
    get:
      tags:
        - Insights
      summary: Get the tenant insight snapshot
      description: >-
        Requires an authenticated tenant session (any permission). Returns one
        coherent, versioned snapshot: the newest (dataset_version,
        model_version) pair with at least one `client_visible` collection, and
        every one of the nine client-facing insight collections at that pair
        (the tenth, `cause_remediation`, is export-only and withheld from this
        response). Each collection reports `ready` (payload present),
        `generating` (materialization pending), or `disabled` (an LLM-derived
        collection with no LLM configured for the tenant). Onboarding-era rows
        only appear if the tenant's `share_onboarding_outputs` flag is on;
        post-go-live ingest rows are always visible regardless of that flag.
      operationId: get_tenant_insight_snapshot_insights_snapshot_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/InsightSnapshot'
components:
  schemas:
    InsightSnapshot:
      properties:
        dataset_version:
          anyOf:
            - type: integer
            - type: 'null'
          title: Dataset Version
        model_version:
          anyOf:
            - type: integer
            - type: 'null'
          title: Model Version
        collections:
          additionalProperties:
            $ref: '#/components/schemas/InsightCollectionState'
          type: object
          title: Collections
        model_ready:
          type: boolean
          title: Model Ready
        all_ready:
          type: boolean
          title: All Ready
        share_onboarding_outputs:
          type: boolean
          title: Share Onboarding Outputs
      type: object
      required:
        - dataset_version
        - model_version
        - collections
        - model_ready
        - all_ready
        - share_onboarding_outputs
      title: InsightSnapshot
    InsightCollectionState:
      properties:
        status:
          type: string
          enum:
            - ready
            - generating
            - disabled
          title: Status
        payload:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          title: Payload
      type: object
      required:
        - status
      title: InsightCollectionState

````