Skip to main content
POST
Roll a flow back to an earlier version
Nothing is overwritten. The old config is written as a new version, so the rollback is itself revertible and the record of what ran when stays intact — the response returns both the restored flow and the version the rollback created.
A version that no longer validates — its enrichment was deleted, its dataset changed — is refused with 400 and the reasons, rather than restoring a graph that would fail on every run.

Headers

x-apikey
string
required

API Key for authentication

Path Parameters

flow_id
string
required

Flow identifier, e.g. fl_ab12cd34

number
integer
required

Version number from GET /v1/flows/{flow_id}/versions

Body

application/json
internal_version
string | null

Optional concurrency check, same semantics as on update.

Response

The restored flow and the version the rollback created

flow
FlowDetail · object
required

A flow plus the pieces needed to edit it. config is the graph, ui is editor-only metadata the runtime ignores, and internal_version is the concurrency token you send back on a write.

version
FlowVersion · object
required

One saved version of a flow. The list arrives newest first, so the first entry is the version the flow is currently on.