Skip to main content
POST
Adopt Content
Moves eligible standalone content you own into the workspace in one transaction. Nothing is copied: identity and version history are kept, and the content’s team shares are removed. Requires writeContent; external editors can adopt only into shared. MCP: workspace_adopt. CLI: rip workspace adopt <workspace-id> <item> --audience … [--kind folder] [--destination-folder-id]. Auth: Authorization: Bearer tr_... (an account API key). {id} is the workspace UUID.

Request body

kind selects the shape:

Response (201)

artifactIds are the public ids of the moved artifacts. folderId is the adopted folder’s id for kind: "folder", otherwise null. Sharing an adopted artifact exposes its complete version history. Adoption is one-way: there is no route that moves workspace content back to standalone ownership.

Errors

Every check runs before any change is made. A workspaceSessionId is validated as described in Shared errors.