ANanzworldline-solutions
Content Delivery

Retrieve content by ID, inode, query, or related content

Changed on

Retrieves contentlets using various lookup strategies. Parameters use a slash-delimited key:value format in the URL path (e.g., /api/content/inode:abc123/live:true/language:1). Supported parameters include: id (identifier), inode, query (Lucene query), type (json or xml), orderby, limit, offset, language, live, depth (0-3 for relationship traversal), render (true to render widgets), related (ContentType.Field:identifier format), and allCategoriesInfo. When 'depth' is set: 0 returns related content identifiers, 1 returns full related content objects, 2 returns related content with their related identifiers, 3 returns related content with their fully hydrated related content.

get/api/content/{params}

Request

Path parameters

paramsstring required

Slash-delimited key:value parameters (e.g., inode:abc123/live:true/language:1)

Response

Content retrieved successfully

object required

Content data in the requested format

Changes

  • 4fd8e917d458Revision changes
    • breaking

      added the pattern .* to the path request parameter params

    • info

      api operation id getContent removed and replaced with getContentLegacy

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the non-success response with the status

    • info

      added the success response with the status