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

# Repo Commits

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

## 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/commits`
- Auth: none declared

The log — one page of it, newest first, with each commit's BODY.

The body is not decoration here. A runtime commit says what work it was in
the subject and then names the run (`turn: run <uuid>`) and every file it
touched with that file's title underneath. Dropping it to save bytes would
throw away the only link between a change and the conversation that caused
it.

`act` is the other axis: not "what changed" but WHAT THE BUSINESS DID. It
matches git's own `--grep` against the `Act:` index line, so finding every
call this month never opens a single commit body — and it composes with
`since`, which is the difference between ~15 ms and ~1 s per 100k commits.

## Path parameters

- `team_id` string, uuid, required

## Query parameters

- `ref` string
- `path` string
- `author` string
- `since` string
- `grep` string
- `act` string
- `skip` integer
- `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)