View

Retrieves a single object of the specified content type by its ID. The object includes the content type's fields as defined by the default edit layout, unless a different layout is specified using layoutId.

This endpoint is a GET request and does not accept a request body. The object to retrieve and the edit layout to use are determined entirely by the URL.

Because the structure of the returned object depends on the selected edit layout and content type, the fields in the response may vary between requests.

Endpoints

Two forms of this endpoint are available.

Using the default edit layout:

GET /{contentType}/{id}

Using a specified edit layout:

GET /{contentType}/{id}/layout/{layoutId}

Examples:

GET /products/1
GET /products/1/layout/2

Note: The available content types depend on the API configuration.

Path Parameters

Parameter	Type	Required	Description
`contentType`	string	Yes	The route of the content type you want to retrieve, such as `products`.
`id`	integer	Yes	The unique identifier of the object to retrieve.
`layoutId`	integer	No	The ID of the edit layout that determines which fields are included in the returned object. Only used with the `/layout/{layoutId}` form of the endpoint. If omitted, the default edit layout is used.

Request Body

None. This endpoint does not accept a request body.

Response

A successful request returns a 200 OK status code and a JSON object containing the requested object's fields.

Status: 200 OK

Content-Type: application/json

Example Response

{
    "id": 1,
    "name": "Wireless Headphones",
    "category": {
        "id": 1,
        "label": "Electronics",
        "route": "products_catgories"
    },
    "price": 79.99,
    "brand": "SoundWave",
    "stock": 45,
    "rating": 4.5,
    "sku": "SW-001",
    "created_at": "2026-10-01T10:00:00.000Z",
    "updated_at": "2026-10-01T10:00:00.000Z",
    "deleted_at": null,
    "author_id": 1,
    "group_id": 1
}

Note: Select fields, such as category in the example above, will be returned as a nested object with their id, label and route rather than a plain identifier.

Data Object

The returned object contains a set of standard system fields. Additional fields are included depending on the requested content type and selected edit layout.

Standard Fields

Field	Type	Description
`id`	integer	The unique identifier of the object.
`created_at`	string	The date and time when the object was created.
`updated_at`	string	The date and time when the object was last updated.
`deleted_at`	string or `null`	The date and time when the object was deleted, or `null` if the object has not been deleted.
`author_id`	integer	The identifier of the author who created the object.
`group_id`	integer	The identifier of the group to which the object belongs.

Timestamps are represented as ISO 8601 strings. For example, 2026-10-01T10:00:00.000Z represents a timestamp in UTC.

Additional Fields

Depending on the selected edit layout and content type, the object may contain additional fields beyond the standard system fields.

In the example above, a product object includes fields such as name, price, brand, stock, rating, and sku. Another content type may expose a different set of properties.

The exact fields, types, and values of these additional properties are determined by the relevant content type and edit layout configuration.

Nested Objects

Some fields may return a nested object instead of a simple value. For example, the category field in the example response contains the following properties:

Field	Type	Description
`category.id`	integer	The unique identifier of the related object.
`category.label`	string	The display label of the related object.
`category.route`	string	The route of the content type the related object belongs to.

Complete Examples

Using the default edit layout

The following example retrieves the product with ID 1 using the default edit layout.

Request

curl -X GET "https://api.example.com/products/1" \
    -H "Authorization: Bearer YOUR_TOKEN"

Response

{
    "id": 1,
    "name": "Wireless Headphones",
    "category": {
        "id": 1,
        "label": "Electronics",
        "route": "products_catgories"
    },
    "price": 79.99,
    "brand": "SoundWave",
    "stock": 45,
    "rating": 4.5,
    "sku": "SW-001",
    "created_at": "2026-10-01T10:00:00.000Z",
    "updated_at": "2026-10-01T10:00:00.000Z",
    "deleted_at": null,
    "author_id": 1,
    "group_id": 1
}

Using a specified edit layout

The following example retrieves the same product using the edit layout with ID 2.

Request

curl -X GET "https://api.example.com/products/1/layout/2" \
    -H "Authorization: Bearer YOUR_TOKEN"

The response is structured in the same way, but the fields included in the object are determined by layout 2.

Replace the following placeholders before sending the request:

products — The content type to retrieve, if supported by the API.
1 — The ID of the object to retrieve.
2 — The ID of the edit layout to use.
YOUR_TOKEN — A valid bearer authentication token.

Notes

Content type determines the endpoint. Replace {contentType} with the specific content type you want to query.
The ID identifies the object. Replace {id} with the identifier of the object to retrieve.
Layout determines the returned fields. The default edit layout is used unless a different edit layout is specified with /layout/{layoutId}.
There is no request body. All parameters are supplied in the URL path.
The response is a single object. Unlike the List endpoint, the response is not wrapped in data or pagination.
Response objects may vary. Do not assume that all content types or layouts return identical object structures.
Timestamps use ISO 8601 formatting. Date and time values are returned as strings, while deleted_at may be null.