Warm Paths warm_paths
One started warm path: where each hop stands and the path as it was ranked (get). Rank, start and cancel paths with committee warm-paths-list and warm-paths-person and account_signals warm-paths-start and warm-paths-cancel.
Call it from an MCP client connected to https://mcp.ken.so/mcp: reads go through warm_paths_read. Each takes operation plus that operation's parameters, and your workspace role decides which operations you see.
Each operation with a route calls the Kenso API at https://api.ken.so with Authorization: Bearer <Kenso API key>, Ken-Version: 1.1 and X-Ken-Workspace-Id: <workspace id>. You can call that route directly with the same headers.
Operations: get
get
Read. Early access: needs accounts, linkedin_network, warm_paths_v2 on for the workspace. GET https://api.ken.so/v1/warm-paths/{warmPathId}
Path: warmPathId
Read one warm path: where each hop stands, and the path as it was ranked.
GET /api/v1/warm-paths/{warmPathId}. Staff; needs the accounts,
linkedin_network and warm_paths_v2 features. Sends Ken-Version 1.1 and
X-Ken-Actor: agent. warmPathId comes from a path of warm-paths-list or
warm-paths-person, from started on warm-paths-list, or from a touch or
approval's warmPathId. Returns data: warmPathId, status (proposed, active,
succeeded, failed, expired, cancelled), shape, accountId, targetKey,
requesterMemberId, startedAt, finishedAt, hops (hop, action, status,
touchId, draftKind, channel, senderMemberId, approverMemberId,
linkedinAccountId, inboxId, recipientPersonId, parts, blurb, outcome) and
path: the ranked path with each hop's from and to named, evidence and
explanation (hops[].index matches hops[].hop), and canCancel (true while
the path is active and the caller is its requester or a workspace admin).
A proposed path has no hops yet. Its requester and the members a hop
names as sender or approver read it; a workspace admin (Manage members)
reads any started path on an account in their scope. Anyone else gets
not_found.