---
title: "Get Datamates"
method: GET
path: "/datamates/"
tags: ["Datamates"]
---

# Get Datamates

`GET /datamates/`

## Request

- Base URL: `https://api.myaltimate.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.myaltimate.com/datamates/`
- Auth: one of:
  - HTTP bearer
  - HTTP bearer

## Response `200`

Successful Response

- GetAllDatamatesResponse
  - `datamates` 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
      - `connection_id` union
        - string
        - integer
      - `connection_ids` string[], nullable
    - `user_id` integer, required
    - `is_owner` boolean, nullable
    - `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
    - `skill_count` integer

## Other responses

- `400`: Invalid request
- `403`: Forbidden

## Changes

- **2026-10-30** `77a7dface13f`: 2 info
  - added the optional property `datamates/items/integrations/items/connection_ids` to the response with the `200` status
  - added the optional property `datamates/items/is_owner` to the response with the `200` status
- **2026-10-27** `883849803623`: 1 info
  - added the optional property `datamates/items/integrations/items/connection_id` to the response with the `200` status
- **2026-09-23** `eebfc2f234e1`: 1 info
  - added the optional property `datamates/items/skill_count` to the response with the `200` status
- **2026-09-04** `51aa5d004c49`: 1 warning
  - added the new `restricted` enum value to the `datamates/items/privacy` response property for the response status `200`

[Operation history](https://skmtc.dev/myaltimate/apis/myaltimate-api/changes/datamates/get.md)

---

[API](https://skmtc.dev/myaltimate/apis/myaltimate-api.md) - [All operations](https://skmtc.dev/myaltimate/apis/myaltimate-api/llms.txt) - [OpenAPI document](https://skmtc.dev/myaltimate/apis/myaltimate-api/revisions/727657ce54e9?raw)