---
title: "Admin Onboarding Conversations"
method: GET
path: "/v1/me/admin/onboarding-conversations"
tags: ["identity"]
---

# Admin Onboarding Conversations

`GET /v1/me/admin/onboarding-conversations`

Every onboarding conversation real people have had, across every shop.

THE PHONE TAB READS THIS. The onboarding a stranger opens from an ad ends in
a browser voice call, and that call is a conversation on an `agent_sessions`
row — it writes no `phone_calls` row, so a phone ledger has nothing to say
about it. This is the list of those conversations, newest first, with the
team they belong to, whether voice was ever heard, how much was said, what
the agent ran, and the calls the shop's line placed afterwards.

One statement, however many workspaces (`onboarding_conversations_across_teams`);
authorisation is `list_customer_teams`' own local-operator gate and the
team list it returns is the exact scope of the read.

`rehearsal` is on every row rather than a filter here: a bench shop
(`created_via = fresh_shop`, owner `…@rehearsal.invalid`) must never read
as a stranger who found the product, and the console decides what to show.
`guest` marks a person who has not signed in yet (`…@guest.invalid`).

## Query parameters

- `per_team` integer
- `limit` integer

## Headers

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

## Response `200`

Successful Response

- object

## Other responses

- `422` — Validation Error

## Changes

> 33 revisions in range; 1 not diffed.

- **2026-09-02** `032c0f4e1565` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/stormy/apis/stormy-control-plane/changes/v1/me/admin/onboarding-conversations/get.md)

---

[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/52151384d62a?raw)