The way you define the kind of content you can edit inside your administrative area passes through the concept of Models, which are much like database tables. For backward-compatibility reasons, the API refers to models as "item types".
RFC 4122 UUID of item type expressed in URL-safe base64 format
"DxMaW10UQiCmZcuuA-IkkA"
Must be exactly "item_type".
Name of the model
"Blog post"
API key of the model
"post"
Whether the model is single-instance or not
Whether editors can sort records via drag & drop or not
Whether this model is a modular content block or not
Whether editors can organize records in a tree or not
If an ordering field is set, this fields specify the sorting direction
Ascending order
Descending order
Specifies the model's sorting method. Cannot be set in concurrency with ordering_field
"created_at"
Order by date of creation
Order by date of last update
Order by date of first publication
Order by date of last publication
Whether draft/published mode is active or not
Whether we require all the project locales to be present for each localized field or not
The way the model collection should be presented to the editors
"compact"
Compact view
Tabular view
A hint shown to editors to help them understand the purpose of this model/block
"Blog posts will be shown in our website under the Blog section"
Whether inverse relationships fields are expressed in GraphQL or not
If this model is single-instance, this tells the single-instance record has already been created or not
The field to use as fallback description for SEO purposes
The way the model collection should be presented to the editors
This field contains a typo and will be removed in future versions: use collection_appearance instead
"compact"
Compact view
Tabular view
If this model is single-instance, this tells the single-instance record has already been created or not
This field will be removed in future versions: instead, use the equivalent has_singleton_item field in the meta collection