---
title: "Suggest Connectable Apps"
method: GET
path: "/v1/teams/{team_id}/connect/suggested"
tags: ["app connect"]
---

# Suggest Connectable Apps

`GET /v1/teams/{team_id}/connect/suggested`

The shelf the connections screen opens on, before anybody has typed.

Owner, 2026-09-17: "have the connection screen with a simple list of all the
toosl ppl might posisbly want to connect adn docn lci kshwo all the toosl
stacticly budilgin" — a list, and not a list we keep in a file. A hardcoded
shelf is stale the week after it is written and offers a plumber the same
tiles it offers a salon, so the products are NAMED by a model from what this
business is, and every one of them is then looked up in the registry, which
stays the only truth about which apps exist.

`about` is what the shell already knows — the workspace's name and the
stations on its rail. It is a HINT and never a key: with nothing at all the
shelf still answers with what any small service business runs, which is the
honest reading of "all the tools people might possibly want to connect".

Already-connected apps ride along so the screen can draw a receipt beside
them instead of offering to connect what is already connected.

## Path parameters

- `team_id` string, uuid, required

## Query parameters

- `about` string
- `limit` integer

## Headers

- `authorization` string, nullable
- `x-darwin-token` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/stormy/apis/stormy-control-plane.md) · [All operations](https://skmtc.dev/stormy/apis/stormy-control-plane/llms.txt) · [OpenAPI document](https://skmtc.dev/stormy/apis/stormy-control-plane/revisions/b09e3c4ee2af?raw)