Skip to main content
PATCH
Update Artifact
Change an artifact’s metadata or history setting without publishing a new version. Only the fields you send change; send at least one. An unknown field is 400 INVALID_FIELD naming it (folderId and isPublic are not fields: use folder and visibility). To change content, publish a version. CLI equivalents: rip artifact patch (title, description, alias, metadata, visibility, --history) and rip artifact move (folder). Auth: Authorization: Bearer tr_...
  • Standalone artifact — the owner, or a member of a team the artifact is shared with.
  • Workspace artifact — a workspace member who can edit its content (writeContent); changing visibility needs share. Editors and admins hold both.

Path parameters

Request body

Example response

A workspace artifact’s response also includes workspaceId and the new workspaceRevision. Every workspace update increments the revision and records what it changed in the workspace change feed: artifact.moved for a folder change, artifact.details_changed for title, description, alias, metadata or history, then artifact.public_access_granted or artifact.public_access_removed when public access changed, each with the same why. A visibility patch naming the current value writes nothing: no revision, no change. A new version (see Publish Version) records artifact.edited.

Errors