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

# Repo View

`GET /v1/teams/{team_id}/repo/views/{path}`

## 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/views/{path}`
- Auth: none declared

Run one view and answer the table.

THE COLUMNS COME FROM THE RECORD, NOT THE QUERY — that is the point of the
feature. A table assembled fresh on every render is a different table every
render, and nobody can build a habit on it.

`ceiling` only ever TIGHTENS what the record declares: a caller rendering on
behalf of a customer says so, and cannot ask for more than the view was
written for. A privileged caller opening a customer-safe view does not
silently widen it either — the record's declared audience is the artifact's
own bound.

## Path parameters

- `team_id` string, uuid, required
- `path` string, required

## Query parameters

- `ceiling` 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)