Makes one revision the published version, the one customers receive, in a single transaction: the revision's configuration is copied onto the journey record, its datasource set onto the published datasources, and name, description, published_at and published_by are stamped onto the revision. Any revision can be published, old or new, so publishing an older revision is the rollback.

name is generated server-side when omitted, so every published revision carries one; an omitted name never replaces a name a previous publish already set. settings.isActive is never changed by a publish.

Only available for organizations with journey versioning enabled; returns 404 otherwise.

{
  "revision_id": "42",
  "name": "Summer campaign"
}

{
  "revision_id": "42",
  "name": "Summer campaign"
}