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. Everyone in the workspace then sees the adopted content. MCP: workspace_adopt. CLI: rip workspace adopt <workspace> <artifact>... | --folder <folder> [--destination-folder-id]. Auth: Authorization: Bearer tr_... (an account API key). {id} is the workspace id or slug (any case; a slug two of your workspaces share is 409 AMBIGUOUS_REFERENCE listing each candidate’s id).

Request body

Send exactly one of artifactIds or folder:

Response (201)

artifactIds are the ids of the moved artifacts. folderId is the adopted folder’s id when you sent folder, otherwise null. Everyone in the workspace can read every version an adopted artifact keeps, and so can anyone with its link once it has public access. 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.