Show examples in:
JavascriptHTTP
Content Management API > Record version

Record version

Every change to a record is stored as a separate record version in DatoCMS.

Object payload

idstring

RFC 4122 UUID of redord version expressed in URL-safe base64 format

Example:"59JSonvYTCOUDz_b7_6hvA"
typestring

Must be exactly "item_version".

meta.created_atdate-time

Date of record version creation

meta.is_publishedboolean

Whether the record version is the published version or not

meta.published_from

Date this version became the published version of the record, or null if it has never been published. May also be null for versions that were published before publication-history tracking was introduced; in that case, fall back to is_published to determine the live status.

Type:date-time, null
meta.published_until

Date this version stopped being the published version of the record (either replaced by a newer published version, or explicitly unpublished). null when the version is currently published or has never been published.

Type:date-time, null
meta.is_currentboolean

Whether the record version is the most recent version or not

item_type

The record version's model

Type:<a href="/docs/content-management-api/resources/item_type">ResourceLinkage&#x3C;"item_type"></a>
item

The record this version belongs to

Type:<a href="/docs/content-management-api/resources/item">ResourceLinkage&#x3C;"item"></a>
editor

The entity (account/collaborator/access token/sso user) who made this change to the record

Type:<a href="/docs/content-management-api/resources/account">ResourceLinkage&#x3C;"account"></a>, <a href="/docs/content-management-api/resources/access_token">ResourceLinkage&#x3C;"access_token"></a>, <a href="/docs/content-management-api/resources/user">ResourceLinkage&#x3C;"user"></a>, <a href="/docs/content-management-api/resources/sso_user">ResourceLinkage&#x3C;"sso_user"></a>, <a href="/docs/content-management-api/resources/organization">ResourceLinkage&#x3C;"organization"></a>
meta.is_validbooleanDeprecated

Whether the record version is valid or not

Validity of a version can only be established in the context of all the current or published item's versions (think about uniqueness validations, for example): use item's is_current_version_valid or is_published_version_valid fields instead.

Available endpoints