---
title: "Admin Browser Voice Calls"
method: GET
path: "/v1/me/admin/browser-voice-calls"
tags: ["identity"]
---

# Admin Browser Voice Calls

`GET /v1/me/admin/browser-voice-calls`

Every browser voice call anyone has had with the product, across every shop.

THE VOICE VIEW READS THIS. A browser call is a WebRTC socket the backend is
not on; what it knows is the `browser_voice` receipt the browser's forwarded
events leave on the conversation — the words, when audio first played, how
long each answer took to become audible, who spoke over whom, the tools the
model called, the provider's errors, and the hang-up. This is that list,
newest first, each row summarised by `browser_voice_receipts.summarize` so
the feed and the open call count the same way.

One statement however many workspaces (`browser_voice_calls_across_teams`);
the scope is exactly `list_customer_teams`' answer. `rehearsal` and `guest`
ride on every row for the reason the onboarding feed gives: a bench shop
must never read as a stranger who found the product, and the console
decides what to show.

## 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/browser-voice-calls/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)