Skip to main content
POST
Rename a team — persists to config, applied on next regen

Authorizations

Authorization
string
header
required

API Key or JWT User Token. If using an API Key, set the X-As-User header to act as a specific user. A JWT User Token is always scoped to a specific user.

Body

application/json

Rename a team by its slug.

Stored in ContextDocConfig.team_overrides and applied at two points during generation: the detection seed (so the stability mechanism remembers the rename) and the post-detection list (so any re-detected old slug is normalized back to the new one).

Both old_slug and new_slug must match [a-z0-9-]{1,64}. new_name is optional — omit to keep the display name the LLM picks.

old_slug
string
required

Current team slug as emitted by detection.

new_slug
string
required

Replacement slug; used in file paths and seed.

new_name
string | null

Optional display name override. Omit to let the LLM pick.

Response

Successful Response

team_overrides
Team Overrides · object
required