Skip to main content
POST
Publish a new artifact version

Authorizations

Authorization
string
header
required

Use Authorization: Bearer <token>. The token is either a user token / OAuth access token, or a service-account API key (cfk_...). A key is valid on every endpoint and acts as its service account, an organization member with per-store permissions. Refused keys answer 403 with Invalid API key., API key revoked., API key expired. or API key disabled..

Path Parameters

project_id
string<uuid>
required

UUID of the project

slug
string
required

Slug of the artifact within the project's catalog

Body

application/json
payload
any
required

Version content; shape depends on the artifact's technical_type. Null clears the artifact.

change_summary
string
short_name
string
Maximum string length: 128

Response

Created

id
string<uuid>
version_number
integer
short_name
string
change_summary
string
edit_source
string

Where the edit came from: "chat", "clara", "mcp", "ui"; empty for legacy/system writes.

coach_conversation_id
string<uuid> | null

Coach conversation whose agent produced this version, when known.

created_at
string<date-time>
created_by_id
string<uuid> | null
created_by_email
string<email> | null
conversation
object | null

Coach conversation that produced this version, when known.

payload
any

Version content; shape depends on the artifact's technical_type. Null allowed.