Rename a team — persists to config, applied on next regen

Persist a team rename.

Fires no regen on its own — the rename applies to the next generated tree. Chain-flattens on write: renaming X→Y where an existing override K→X exists rewrites that to K→Y and still records X→Y, so future lookups are always one hop deep.

POST /context-documents/teams/rename

Rename a team — persists to config, applied on next regen

cURL

curl --request POST \
  --url https://api.hyperspell.com/context-documents/teams/rename \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "old_slug": "<string>",
  "new_slug": "<string>",
  "new_name": "<string>"
}
'

200

{
  "team_overrides": {}
}

Authorizations

APIKeyAsUser

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

200

application/json

Successful Response

team_overrides · Team Overrides · object · required

Show child attributes