Show examples in:
Javascript HTTP
Content Management API > Record version

Record version

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

Object payload

id string

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

Example: "59JSonvYTCOUDz_b7_6hvA"
type string

Must be exactly "item_version".

meta.created_at date-time

Date of record version creation

meta.is_published boolean

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_current boolean

Whether the record version is the most recent version or not

item_type

The record version's model

item

The record this version belongs to

editor

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

meta.is_valid boolean Deprecated

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