v1
protected
workspace-config
Export Workspace Config
Changed onExport the current workspace in the canonical Bundle YAML format.
The output is accepted by the bundle Analyze and Install flow and can include agents, MCPs, skills, cron automations, and supported webhook channels. MCP credentials and Telegram tokens are setup-field references, never exported values. Provider configurations are not represented by the Bundle schema; configure them separately in the destination workspace.
The response is served as text/plain so generated API clients receive the YAML body as a string.
get/v1/workspaces/{workspace}/export
Request
- The document declares no server URL.
- AuthHTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
workspacestring required
Slug of the workspace the request acts in
Response
Successful Response
Changes
- info
endpoint added
- info