Skip to main content
POST
Publish an older version again

Authorizations

X-API-Key
string
header
required

A Streamloop API key (sl_…). It carries no workspace: send X-Workspace-Id too (400 WORKSPACE_REQUIRED otherwise).

Headers

Idempotency-Key
string

Retry safely: the key (per caller, workspace, method and path) is taken before the request runs, and its first answer is replayed for 24 hours, with Idempotency-Replayed: true — a repeat sent while the first still runs waits for it. The same key with a different body is 422 IDEMPOTENCY_KEY_REUSED. A 5xx is not kept: the retry runs.

Maximum string length: 200
If-Match
string

The published version you saw, instead of expectedVersion

X-Workspace-Id
string

The workspace to act in. Required with an API key; otherwise the session's own.

Path Parameters

id
string
required

The scene's id (scn_…)

Pattern: ^scn_

Body

application/json
version
integer
required

A published version's number (0 or less: 422 INVALID_INPUT; one that doesn't exist: 404)

Required range: x >= 1
expectedVersion
integer

The latest published version you saw (required, or If-Match)

Required range: x >= 0
confirm
boolean

I accept what CONFIRM_REQUIRED named: viewers see this at once

Response

Published

version
integer

The published version after this call. On a dry run it is unchanged (0: never published) and the draft would become the next one

summary
string

What happened and what comes next, in a sentence

publishedAt
string<date-time> | null

null on a dry run of a scene never published

unchanged
boolean

The draft was what is published already: no new version

changes
string[]

What changed since the previous version, as resource paths (change frame/main/title props.value, add source/data/hn)

dryRun
boolean

Only checked: nothing was published

notes
string[]

What to know about this publish: edits a pinned draftRevision left in the draft, a revert's draft

stale
boolean

The draftRevision was an older one: the draft has changed since, and those changes are not published