Every Loops API call is authenticated with BASETEN_API_KEY. Resources nest as: sessions own runs and samplers; runs own checkpoints; deployments are produced from checkpoints.
Most routes live under /v1/loops and run in your organization’s default team. To provision or list resources in a specific team instead, use the team-scoped routes under /v1/teams/{team_id}/loops — the Loops Python SDK calls these when you pass a team_id.
Each route’s request body, query parameters, response shape, and an interactive playground live on its own page in this section. This overview covers the resource model. Pass your key as Authorization: Bearer $BASETEN_API_KEY; the playground on each route page prefills this header.
Both the HTTP API and the Python SDK identify a trainer by its run_id.
