app connect

Search Connectable Apps

Search the live registry for apps this team could connect.

Until this route existed the registry was reachable only by GUESSING a slug and reading the 404 body of connect/link — so "find out what they already run and offer to connect it" was an unrunnable instruction. The search is the registry's own, never a list maintained here.

IT ANSWERS A DESCRIPTION AS WELL AS A NAME, and the second one is what the product actually asks. The registry is a NAME index: a shop that says "our books" or "accounting and invoicing" matched nothing at all, and the miss came back 200 with zero rows — which the onboarding face draws as a spinner that never stops. So a phrase the index cannot answer goes once through connect_intent, which names the products and looks each one back up here. The name search is still tried FIRST and unchanged, so a caller that knows what it wants pays nothing for the lane, and matched says which one answered.

get/v1/teams/{team_id}/connect/apps

Request

  • Base URL: https://api.stormy.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.stormy.ai/v1/teams/{team_id}/connect/apps
  • Auth: none declared

Path parameters

team_idstring uuid required

Query parameters

qstring required
limitinteger

Headers

authorizationstring nullable
x-darwin-tokenstring nullable

Response

Successful Response

object required

Changes

No operation changes recorded.