Try our new Setup Skill to automatically integrate Hyperspell into your project
API Documentation
Memories
Messages
Traces
Authentication
Daemon
Integrations
Connections
Folder Policies
Vault
Context Documents
- GETList conflicts for the authenticated app
- POSTApprove or reject a pending conflict
- GETEvent log for a conflict
- POSTManually trigger conflict detection for a tree
- POSTGenerate a context document
- GETPreview available data for context document generation
- GETList context documents
- GETGet a context document
- POSTGenerate context docs folder structure in Google Drive
- POSTGenerate a three-tier context document tree
- GETGet tree generation progress
- GETGet the latest context document tree
- GETGet a specific context document tree by tree_id
- POSTPublish a COMPLETED tree (require_review flow)
- PATCHEdit files in a context document tree
- POSTRename a team — persists to config, applied on next regen
- GETList active team rename overrides
- DELClear a team rename override
- GETList persisted user edits for an app
- POSTLLM-based three-way merge of a user edit with the current LLM output
- POSTMark the user's decision on an edit — records which baseline they reviewed
- DELClear (soft-archive) a persisted edit
- GETDiff a tree against the previous tree
- GETCheck staleness of context documents
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>"
}
'{
"team_overrides": {}
}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.
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>"
}
'{
"team_overrides": {}
}Documentation Index
Fetch the complete documentation index at: https://docs.hyperspell.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
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
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.
Response
Successful Response
Show child attributes
Show child attributes
Was this page helpful?