Skip to main content

Workspaces API

Workspace list, creation, selection, home, and by-slug proxy behavior.

How To Use This API Group

Use this group when a client needs to work with workspaces behavior in Veoveo. Start with the route list, choose the method that matches the user task, then open the API reference for exact parameters and schemas.

Authentication And Scope

Most workspace routes require a signed-in session or an integration token with access to the target workspace. Keep the workspace reference and resource references from prior responses or visible app routes.

Current Routes

MethodPathSummaryAuthSurface
GET/api/wList workspacessessionbrowser_api
POST/api/wCreate workspacesessionbrowser_api
GET/api/w/homeGet selected workspace homesessionbrowser_api
POST/api/w/selectSelect workspacesessionbrowser_api
GET/api/workspacesList workspacessessionbrowser_api
POST/api/workspacesCreate workspacesessionbrowser_api
GET/api/workspaces/by-slug/{workspace_ref}/{tail}Proxy workspace route by slugsession, user_api_token, workspace_service_tokenbrowser_api
POST/api/workspaces/selectSelect workspacesessionbrowser_api

Representative Request

This example uses one workspaces route. Replace bracketed path values with ids from prior API responses and use the reference for the exact request body and response schema.

curl -sS \
-H "Authorization: Bearer <token>" \
"https://veoveo.ai/api/w"

Response Review

  • Check status codes and structured error details before retrying.
  • Treat returned identifiers as the values to use in follow-up calls.
  • For routes that create or update workspace facts, review the affected artifact, event, link, bot, or operation in the app.

Media To Add

  • Table: common workspaces calls with required references, expected result, and next review action. It helps developers choose the right route quickly. Source: this route group and the API reference.