Content Type

A Content Type is the template (schema) that content follows. It defines which fields the content has and, for each field, its type, whether it is localized, whether it is required, and its validation rules. Take a "Product" in a clothing store as an example: a single Content Type "Product" defines the set of attributes such as product name, price, description, and photo, while each individual product is created as a Content that follows this template.

In CMA, a Content Type is a sub-resource of Space, and its path is based on /spaces/{spaceId}/content-types. Management operations such as create, update, and unpublish are performed on CMA, and the published snapshot is delivered through CDA. Note that a Content Type is published automatically on create and update, so unlike Content it reaches the Published status right away without a separate publish call (see Status and automatic publishing below).

Resource structure

The following is the single-read response for the Content Type "Product". Along with sys (system properties), it has body properties such as name, displayField, publishWithAuthor, and fields.

{
  "sys": {
    "id": "3trmXRM3RqbgSnifyg7PAmlxvX4fGY",
    "type": "ContentType",
    "space": { "sys": { "id": "tcq4V2Xb", "type": "Refer", "targetType": "Space" } },
    "publish": {
      "version": 7,
      "at": "2026-06-18T03:05:11.453Z",
      "firstAt": "2026-06-17T16:22:01.081Z",
      "counter": 4,
      "by": { "sys": { "id": "3p4tcFbQRwz503VXdtHXNI5dZH5TVB", "type": "Refer", "targetType": "User" } }
    },
    "createdBy": { "sys": { "id": "3p4tcFbQRwz503VXdtHXNI5dZH5TVB", "type": "Refer", "targetType": "User" } },
    "createdAt": "2026-06-17T16:22:01.047Z",
    "updatedBy": { "sys": { "id": "3p4tcFbQRwz503VXdtHXNI5dZH5TVB", "type": "Refer", "targetType": "User" } },
    "updatedAt": "2026-06-18T03:05:11.453Z",
    "version": 8,
    "status": "Published"
  },
  "name": "Product",
  "displayField": "productName",
  "publishWithAuthor": false,
  "fields": [
    { "id": "3hzbux8gsnb4h", "name": "Product Name", "apiName": "productName", "type": "ShortText", "localized": true, "required": true, "validations": [], "disabled": false },
    { "id": "4usptben4t1z", "name": "Price", "apiName": "price", "type": "Long", "localized": false, "required": false, "validations": [], "disabled": false },
    { "id": "21zuem8be6o6j", "name": "Description", "apiName": "description", "type": "RichText", "localized": true, "required": false, "validations": [], "disabled": false },
    { "id": "2mr5ylgtheegr", "name": "Photo", "apiName": "photo", "type": "Refer", "localized": false, "required": false, "validations": [], "disabled": false, "targetType": "Media" },
    {
      "id": "5bpmiwo2woq8",
      "name": "Brand",
      "apiName": "brand",
      "type": "Refer",
      "localized": false,
      "required": false,
      "validations": [
        { "referContentType": [ { "sys": { "id": "3trmXRM3RqbgSnifyg7PLjv7PDSdHg", "type": "Refer", "targetType": "ContentType" } } ] }
      ],
      "disabled": false,
      "targetType": "Content"
    }
  ]
}

Key properties:

• sys.id: The unique identifier of the Content Type. It goes into {contentTypeId} in the single-read, update, and delete paths.
• name: The name of the Content Type (e.g. Product).
• displayField: The apiName of the field used to represent each Content in the content studio list (e.g. productName).
• publishWithAuthor: Whether to include author information when a Content is published. The default is false.
• fields: The list of fields this template defines. The structure of each entry is described in Fields below.

The photo field has type Refer and targetType Media, so it points to an uploaded file asset. The brand field is Refer + targetType: Content, and the referContentType in validations restricts it to reference only Content of a specific Content Type (here, "Brand").

System properties (sys)

Every Content Type carries common system properties and Content Type specific properties in the sys object. space, createdBy, and updatedBy are in the Refer shape ({ "sys": { "id", "type": "Refer", "targetType" } }).

Keys of the publish object:

When you unpublish (DELETE .../publish), version, at, and by are removed from publish, leaving only firstAt and counter.

A Content Type's sys does not have the contentType (self-reference) property found in a Content's sys, because a Content Type is itself the template. It also has no archive property.

Fields

fields is the list of fields this Content Type defines. Each entry has the following structure (FieldDefinition).

Field types (type)

type determines how the value is stored and retrieved. Some types behave differently in search.

In the "Product" example, Product Name is ShortText, Price is Long, Description is RichText, Photo is Refer (targetType: Media), and Brand is Refer (targetType: Content).

Validations (validations)

validations is an array of rules to apply to the field value. Each entry holds one of the following keys.

Values usable in mediaMimetypeGroup (12 of them): Attachment, Plaintext, Image, Audio, Video, RichText, Presentation, Spreadsheet, PdfDocument, Archive, Code, Markup.

The brand field in the "Product" example uses referContentType to restrict references to only the "Brand" Content Type (whose sys.id is 3trmXRM3RqbgSnifyg7PLjv7PDSdHg).

Status and automatic publishing

A Content Type is published automatically on create, update, and partial update. This differs from Content. A Content only enters the delivery path after a separate publish call following creation, whereas a Content Type's create response comes back as status: "Published" right away.

status is one of the following four values.

sys.version increases by 1 with every change. Because a Content Type is updated and published at once, a single update raises version by 2 (the update itself +1, the automatic publish +1). In the "Notice" example, version is 2 right after creation (create +1, automatic publish +1) and publish.counter is 1. After a subsequent update, version becomes 4 and publish.counter becomes 2.

The only path by which a Content Type becomes Draft is an explicit unpublish (DELETE .../publish). When you unpublish, status becomes Draft, and version, at, and by are removed from the publish object, leaving only firstAt and counter.

Constraints

Delete guard: Deletion must satisfy both conditions.

• If even one Content uses this Content Type, it cannot be deleted (WGL422010). Delete all such Content first. This check is evaluated first.
• A Content Type in a published state (Published/Changed) cannot be deleted directly (WGL422009). Unpublish it first (DELETE .../publish) to make it Draft, then delete it (an Archived Content Type can also be deleted).

API

The base URL for all endpoints below is https://cma.weegloo.com/v1, and a Bearer token that authenticates against CMA is required in the Authorization header. Update, partial update, publish, and unpublish must also send the X-Weegloo-Version header (the current resource's sys.version) for optimistic concurrency control.

Related documents

• Content modeling: How to create a Content Type in the content studio.
• Status and publishing: What publishing and versions mean.