team repo
Repo View
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.
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
Path parameters
team_idstring uuid required
pathstring required
Query parameters
ceilingstring
limitinteger
Headers
authorizationstring nullable
x-darwin-tokenstring nullable
Response
Successful Response
object required
Changes
No operation changes recorded.