team repo
Repo Calendar
Every clock this workspace runs on, over one window.
Bookings come from the tree through the SAME projection the desk reads, so the grid cannot disagree with what the agent was told — a calendar built from its own query is a second source of truth, and this architecture has spent its whole life removing those.
A TEAM WITH NO TREE IS THE EMPTY STATE, not a 404, for the same reason /overview gives one: a workspace nobody has written into is a normal row.
get/v1/teams/{team_id}/repo/calendar
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/calendar
- Auth: none declared
Path parameters
team_idstring uuid required
Query parameters
fromstring
tostring
Headers
authorizationstring nullable
x-darwin-tokenstring nullable
Response
Successful Response
object required
Changes
No operation changes recorded.