Mavera DocsReference
Checking your Mavera sessionLoading workspace audiences and API keys…
Checking…Use or share this pageSend the page itself, print it, or open its complete context in your AI workspace.
Projects & folders
Workspace organization.
Projects
| Endpoint | Does |
|---|---|
POST /api/v1/tools/create_project | Create a project. Body: { name, description? }. |
POST /api/v1/tools/list_projects | List projects. { includeArchived? }. |
POST /api/v1/tools/update_project | Rename / re-describe / archive. { projectId, name?, description?, status? }. |
Conversations
file_conversation | Move a chat into a project — or projectId:null to unfile. { conversationId, projectId }. |
update_conversation | Rename, tag, or archive. { conversationId, title?, tags?, archived? }. |
list_conversations | Filter by project, unfiledOnly, text query, includeArchived. |
# File a chat into a project, then tag it
POST /api/v1/tools/create_project { "name": "Q3 Pricing" } # → { project: { id: "proj_…" } }
POST /api/v1/tools/file_conversation { "conversationId": "chat_abc", "projectId": "proj_…" }
POST /api/v1/tools/update_conversation { "conversationId": "chat_abc", "tags": ["pricing","smb"] }Everything here is workspace-scoped: a key can only see and organize its own workspace's projects and conversations. Filing into a project from another workspace is rejected.