---
title: "Get Datamate Summary"
method: GET
path: "/datamates/{datamate_id}/summary"
tags: ["Datamates"]
---

# Get Datamate Summary

`GET /datamates/{datamate_id}/summary`

## Path parameters

- `datamate_id` integer, required

## Query parameters

- `start_date` string, date-time
- `end_date` string, date-time

## Response `200`

Successful Response

- GetDatamateWithStatsResponse
  - `datamate` DatamateModel, required
    - `id` integer, nullable
    - `name` string, required
    - `description` string, nullable
    - `integrations` DatamateIntegration[], required
      - `id` union, required
        - string
        - integer
      - `tools` DatamateIntegrationTool[], required
        - `key` string, required
    - `user_id` integer, required
    - `memory_enabled` boolean
    - `knowledge_engine_enabled` boolean
    - `privacy` 'private' | 'public' | 'restricted' — Sharing modes for a workspace. Deliberately local rather than adding a member to the shared ``PrivacySetting``, which is imported by five resources (datamates, knowledge bases, notebooks, query bookmarks, custom skills). ``restricted`` is meaningless for the other four, and widening the shared enum would make it a legal value there. The two overlapping values keep identical strings, so rows written before this existed, and every cross-file read that compares against ``PrivacySetting.PUBLIC.value``, still work. Reviewers found this argument was made and then broken in the same diff: four ``CustomSkill`` schemas were swapped to this enum, which made ``restricted`` a legal value for a resource with no grant table behind it — ``_visible_to`` (``crud/custom_skills.py``) matches owner-or-public only, and ``custom_skills.privacy`` has no CHECK, so such a skill would persist and be permanently invisible to everyone but its creator. Custom skills are back on ``PrivacySetting``; keep them there until they implement sharing.
    - `knowledge_bases` integer[], nullable
    - `created_at` string, date-time, nullable
    - `skills` DatamateSkill[], nullable
      - `id` string, required
      - `name` string, required
      - `description` string, required
      - `content` string, required
      - `priority` integer, required
      - `related_tools` string[], nullable
      - `source` string, required
      - `integration_id` string, nullable
      - `always_active` boolean, required
  - `usage` DatamateUsageItem, required
    - `assists` integer
    - `guardrails` integer
  - `events` DatamateAuditEventModel[], required
    - `id` integer, required
    - `event_type` string, required
    - `user_id` integer, required
    - `tool_name` string, required
    - `integration_id` string, required
    - `payload` object, required
    - `teammate_id` string, required
    - `timestamp` string, date-time, required
    - `created_at` string, date-time, required
  - `created_at` string, date-time, required
  - `last_used_at` string, date-time, nullable

## Other responses

- `400` — Invalid request
- `403` — Forbidden
- `422` — Validation Error

## Changes

- **2026-09-04** `51aa5d004c49` — 1 warning
  - added the new `restricted` enum value to the `datamate/privacy` response property for the response status `200`

[Change history](https://skmtc.dev/myaltimate/apis/fastapi/changes/datamates/:datamate_id/summary/get.md)

---

[API](https://skmtc.dev/myaltimate/apis/fastapi.md) · [All operations](https://skmtc.dev/myaltimate/apis/fastapi/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/myaltimate/fastapi/revisions/51aa5d004c49/schema)