AEM 6.4 has reached the end of extended support and this documentation is no longer updated. For further details, see our technical support periods. Find the supported versions here.
AEM Content Services are designed to generalize the description and delivery of content in/from AEM beyond a focus on web pages.
They provide the delivery of content to channels that are not traditional AEM web pages, using standardized methods that can be consumed by any client. These channels can include:
With content fragments that use structured content, you can provide content services by using the JSON exporter to deliver the contents of an(y) AEM page in JSON data model format. This can then be consumed by your own applications.
The functionality described here is available for all Core Components since release 1.1.0 of the Core Components.
Using the AEM JSON exporter you can deliver the contents of an(y) AEM page in JSON data model format. This can then be consumed by your own applications.
Within AEM the delivery is achieved using the selector model
and .json
extension.
.model.json
For example, a URL such as:
http://localhost:4502/content/we-retail/language-masters/en.model.json
Will deliver content such as:
You can alternatively deliver the contents of a structured content fragment by targeting it specifically.
This is done using the entire path to the fragment (via the jcr:content
); for example with a suffix such as.
.../jcr:content/root/responsivegrid/contentfragment.model.json
Your page can contain either a single content fragment or multiple components of various types. You can also use mechanisms such as list components to automatically search for relevant content.
For example, a URL such as:
http://localhost:4502/content/we-retail/language-masters/en/manchester-airport/jcr:content/root/responsivegrid/contentfragment.model.json
Will deliver content such as:
You can adapt your own components to access and use this data.
Although not a standard implementation, multiple selectors are supported, but model
must be the first.
See also:
Assets HTTP API
Sling Models:
AEM with JSON:
For further details see: