---
title: "List Connections"
method: GET
path: "/connections/"
tags: ["connections"]
---

# List Connections

`GET /connections/`

## 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/connections/`
- Auth: one of:
  - HTTP bearer
  - HTTP bearer

List the caller's connections, and with ``include_shared`` those shared
with them.

Own-only by default, as before sharing existed: the MCP engine and the VS
Code extension read this list as "my connections" and pick a default from
it, so connections shared with the caller are opt-in here.

## Query parameters

- `include_shared` boolean: Also list connections shared with the caller, read-only and without their secret fields

## Response `200`

Successful Response

- ConnectionListResponse
  - `connections` ConnectionInDB[], required
    - `name` string, required
    - `integration_id` string, required
    - `config` object, required
    - `id` integer, required
    - `user_id` integer, required
    - `is_valid` boolean, required
    - `last_validated_at` string, date-time, nullable
    - `created_at` string, date-time, required
    - `updated_at` string, date-time, nullable
    - `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.
    - `is_owner` boolean
    - `unreadable_secret_fields` string[]
    - `owner` ConnectionOwner
      - `id` integer, required
      - `name` string, required
    - `shares` ConnectionShares
      - `user_ids` integer[], required
      - `team_ids` integer[], required

## Other responses

- `422`: Validation Error

## Changes

- **2026-10-27** `883849803623`: 7 info
  - added the new optional `query` request parameter `include_shared`
  - added the non-success response with the status `422`
  - added the optional property `connections/items/is_owner` to the response with the `200` status
  - added the optional property `connections/items/owner` to the response with the `200` status
  - …3 more

[Operation history](https://skmtc.dev/myaltimate/apis/myaltimate-api/changes/connections/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)