Show examples in:
Javascript HTTP

Content Management API > Record

Record

DatoCMS stores the individual pieces of content you create from a model as records, which are much like table rows in a database. For backward-compatibility reasons, the API refers to records as "items".

You can learn how the records are structured at the API level, and everything that is necessary to interact with the records through CMA in the following detail sections:

Object payload

id string

RFC 4122 UUID of record expressed in URL-safe base64 format

Example: "hWl-mnkWRYmMCSTq4z_piQ"
type string

Must be exactly "item".

meta.created_at date-time

Date of creation

meta.updated_at date-time

Last update time

meta.published_at

Date of last publication

Type: null, date-time
meta.first_published_at

Date of first publication

Type: null, date-time
meta.publication_scheduled_at

Date of future publication

Type: null, date-time
meta.unpublishing_scheduled_at

Date of future unpublishing

Type: null, date-time
meta.status null, enum

Status

Example: "published"
draft

The record is not published

updated

The record has some unpublished changes

published

The record is published

meta.is_current_version_valid null, boolean

Whether the current version of the record is valid or not

meta.is_published_version_valid null, boolean

Whether the published version of record is valid or not

meta.current_version string

The ID of the current record version

Example: "4234"
meta.stage null, string

Workflow stage in which the item is

relationships.item_type.data

The record's model

relationships.creator.data

The entity (account/collaborator/access token/sso user) who created the record

meta.is_valid boolean Deprecated

Whether the current record is valid or not

This field will be removed in the future: use is_current_version_valid or is_published_version_valid instead, according to the specific use case

Available endpoints