We're considering using this HTTP Assets API for Content...

[kautuk_sahni]

Content Fragments Support in AEM Assets HTTP API by Adobe

Abstract

The Adobe Experience Manager (AEM) Assets REST API allows developers to access content (stored in AEM) directly over the HTTP API, via CRUD operations (Create, Read, Update, Delete).

The API allows you to operate AEM as a headless CMS (Content Management System) by providing Content Services to a JavaScript front end application. Or any other application that can execute HTTP requests and handle JSON responses.
For example, Single Page Applications (SPA), framework-based or custom, require content provided over the HTTP API, often in JSON format.
While AEM Core Components provide a very comprehensive, flexible and customizable API that can serve required Read operations for this purpose, and whose JSON output can be customized, they do require AEM WCM (Web Content Management) know-how for implementation as they must be hosted in (API) pages that are based on dedicated AEM templates. Not every SPA development organization has access to such resources.

This is when the Assets REST API can be used. It allows developers to access assets (for example, images and content fragments) directly, without need to first embed them in a page, and deliver their content in serialized JSON format. (Note that it is not possible to customize JSON output from the Assets REST API). The Assets REST API also allows developers to modify content - by creating new, updating, or deleting existing assets, content fragments and folders.

Read Full Blog

Content Fragments Support in AEM Assets HTTP API

Q&A

Please use this thread to ask the related questions.

[anjali_biddanda]

We're considering using this HTTP Assets API for Content Fragments. This API endpoint will be consumed by channels. (Apps, Salesforce etc). However this Assets API only captures dc namespace metadata from the metadata node. Metadata such as lastReplicated date from the jcr:content node of asset is not captured. The need for this lastReplicated date is so that channels only retrieve the CF if it has changed, if not, the cached version at their end is used. 

As I understand this OOTB Assts API cannot be customised. We're looking into other approaches but it seems an overkill to replicate this functionality with a lastReplicated date added. This would be a good feature add to consider.

Has this been raised before, or am I missing something? Would you have any suggestions?

Thanks for your time.

[Naga_Seran]

Hi All,

We have an internal tool to update content fragment using Asset API. We found that jcr:lastModified and jcr:lastModifiedBy information is not updating while making updates to content fragment using AEM asset api. We tried to add modifiedBy & modified properties in request body but no luck. Could you please advise on this