Overview
A Content Version is a single rendition of a Content Instance, identified by language × environment × status. Versions are what make content multi-language and multi-environment: the same instance can hold an English and a Spanish version, a production and a development environment, and a draft alongside what’s published — each a separate version. An instance’s actual content (its attribute values) lives on its versions, not on the instance itself. For the bigger picture, see the Content overview.Where to find it
Versions are authored from a Content Instance: the instance’s editor has a version header to pick the language and environment and to see the publication status, and the content fields you edit belong to the active draft version.Properties
| Property | Type | Required | Description |
|---|---|---|---|
language | string | Yes | The version’s language, e.g. en, es. |
environment | string | Yes | The version’s environment, e.g. production, development. |
status | enum | Yes | draft or published. |
title | string | No | Defaults to the instance’s title. |
slug | string | No | Defaults to the instance’s slug. |
scheduled_to_publish_at | datetime | No | When the version is scheduled to publish. |
scheduled_to_unpublish_at | datetime | No | When the version is scheduled to unpublish. |
| (attribute values) | mixed | — | The instance’s content fields for this language/environment, validated against the template’s attributes. |
A version is uniquely identified by the combination of language,
environment, and status — you can’t have two
draft versions for the same
en / production pair, but you can have a draft and a published one.Lifecycle
Content is authored as a draft, then promoted to published:| Operation | What it does |
|---|---|
| Create / update | Author or edit a draft version for a language and environment. |
| Publish | Copy the draft into the published version, replacing what was live. |
| Unpublish | Remove the published version; the draft stays. |
| Restore draft | Copy the published version back over the draft, discarding draft edits. |
| Propagate | Copy a version’s content to other languages or environments as a starting point. |
Scheduling
A version’s publish and unpublish can be scheduled instead of done by hand — either with manual dates or by pointing the schedule at a Publishing Window (a reusable start/end range). The version then goes live and comes down automatically.Attributes
A content family’s custom fields are defined against the Content Version object type and scoped to the Content Template. That’s why content lives on versions: each version carries its own attribute values, so the English draft and the Spanish published version can differ field by field.Seeds
Versions don’t seed on their own — they travel with their instance. In an instance Seed, each record’sversions array carries
the per-language/environment content (see
Content Instances). The version attributes
themselves are defined structurally, against the content_versions object type
and scoped to the template — see the
structural seed example.
Governance & permissions
Versions follow the same rules as their Content Instance: a super admin or Master can manage any version, and a Journey Manager can author, publish, and unpublish versions of the instances they own.API access
Versions are managed through the instance’s version operations — create/update, publish, unpublish, restore draft, propagate, list available versions, and schedule publish/unpublish. See the API reference.Related
Content Instances
The record a version belongs to.
Publishing Windows
Schedule when a version goes live.
Attributes
The fields a version carries.
Events & Automation
React to publish / unpublish events.