Skip to main content
POST
Fork Artifact
Fork an artifact into an independent copy owned by you. Content is not duplicated — the fork reuses the source version’s storage. The fork records its source: parentArtifactId names the source artifact, and forkedFrom ({ artifactId, versionId, version }) the exact version copied, by id and number, on this response and every read of the fork. forkedFrom is null when you can no longer read the source. A fork of a standalone artifact is a standalone artifact with link visibility. A fork of a workspace artifact by a member who can write there stays in the same workspace, members only (private), where everyone in the workspace sees it. Anyone else can fork a public workspace artifact (visibility: "link"): the fork is a standalone copy in their own account, with link visibility, no why and no workspace change. Auth: Authorization: Bearer tr_.... You must be able to read the source: link and public artifacts can be forked by anyone; a private one by its owner or a member of a team it is shared to. Forking a workspace artifact needs edit access to it, unless it is public (link).

Request body

Example response

The response has the same shape as Create Artifact: folder_id and folder name the folder the copy was filed in (folder is { slug, teamSlug? }, or null when unfiled), and forkedFrom names the version copied.

Errors

The fork does not sync with its source. Later versions of either artifact do not affect the other.