Skip to main content
POST
Update Asset

Authorizations

api_key
string
header
required

Body

application/json
uuid
string
required

UUID of the asset to update. e.g. '4f1e2a90-8b3d-4c21-9e07-2a1b3c4d5e6f'

identifier
string

New identifier/slug. e.g. 'q3-launch-microsite'

Required string length: 1 - 255
description
string

New description. e.g. 'Updated Q3 launch page'

Minimum string length: 1
entryPoint
string

New entry file served at the root. e.g. 'index.html'

Required string length: 1 - 255
privacy
enum<string>

New privacy tier — an ordered ladder, each strictly more permissive: only_me (owner only), workspace (owner + workspace members), public (anyone with the URL). e.g. 'public'

Available options:
only_me,
workspace,
public
status
enum<string>

New lifecycle status. One of: published, unpublished. Independent of privacy — this does NOT make an asset public or private; use privacy for that. e.g. 'published'

Available options:
published,
unpublished
vanitySlug
string | null

Vanity slug for a friendly URL — unique within the workspace; the server answers 409 (conflict) when another asset already holds it. Setting one gives the asset a vanityUrl; pass null to clear the slug (and its vanityUrl). e.g. 'q3-launch'

Minimum string length: 1

Response

Asset updated successfully

_metadata
object
required
data
object
required