---
title: "Call Processing"
method: GET
path: "/v1/teams/{team_id}/repo/call-processing"
tags: ["team repo"]
---

# Call Processing

`GET /v1/teams/{team_id}/repo/call-processing`

WHAT A CLOSED CALL IS BECOMING, while it becomes it (owner, 2026-09-23:
the page after a call showed a loader for minutes, "not even pointing to
anything while it's PROCESSING").

Read-only. The call's owed work (`browser-call-page:<call>`) names its
session, so the recording can play at once; the closeout's own session is
derived from the call, so its durable tool events say what it is doing;
the tree says whether the record is filed and whether its page is drawn.

## Path parameters

- `team_id` string, uuid, required

## Query parameters

- `call` string, uuid, required

## 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-24** `92d7c7c2b732` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/stormy/apis/stormy-control-plane/changes/v1/teams/:team_id/repo/call-processing/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)