---
title: "Repo Files"
method: GET
path: "/v1/teams/{team_id}/repo/files"
tags: ["team repo"]
---

# Repo Files

`GET /v1/teams/{team_id}/repo/files`

## 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}/repo/files`
- Auth: none declared

Every path in the tree, flat, from ONE `ls-tree -r`.

The directory listing is deliberately one level at a time; this is the other
question — "what does this workspace contain, everywhere" — and answering it
by walking `/tree` per folder is N round trips for something git prints in
one.

It exists because the media view has to JOIN. An R2 recording knows its call
id and nothing else; the document that explains that call is a path in here
(`customer/sms-14155550188/calls/2026-08-08-call-99f26478.md`). One read of
the path list turns a bucket of audio files into a customer's history.

## Path parameters

- `team_id` string, uuid, required

## Query parameters

- `ref` string
- `prefix` string
- `limit` integer

## Headers

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

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[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/4d811ab18158?raw)