Assets HTTP API with Content Fragments on 6.4 | Community
Skip to main content
christopher_jo4
christopher_jo4
New Participant
April 9, 2019
Solved

Assets HTTP API with Content Fragments on 6.4

  • April 9, 2019
  • 6 replies
  • 1726 views

Hopefully I haven't missed any relevant documentation, but had a question regarding the Assets HTTP API with Content Fragments on 6.4.

It's my current understanding that AEM 6.5 introduces better support for Content Fragments via the Assets HTTP API:

Adobe Experience Manager Help | Using HTTP API with AEM Content Fragments

Is there any intention of bringing this support to AEM 6.4 via a service pack or cumulative fix pack?

Just exploring my options for an upcoming project.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Gaurav-Behl

Per my understanding this is already available in 6.4 and would have updated features w.r.t CF and other things in 6.5.  I'm able to access

http://localhost:4502/api/assets/<asset_path>.json and get the listing

e.g. http://localhost:4502/api/assets/we-retail/en/experiences/48-hours-of-wilderness/48-hours-of-wilderness.json

check -

Assets HTTP API

6 replies

A
alistairp781078
New Participant
January 21, 2021

Bumping this thread to see if anyone has any additional information about the original request given we're now almost two years down the line.

 

I'm working with content fragments that I would like to inspect via the assets API. We're still only on 6.4, which only supports exposing metadata about the fragments rather than the properties/content of it unlike in 6.5.

 

Does anyone know if there's a feature pack that we can install on 6.4 to extend the functionality of the assets API in line with 6.5?

christopher_jo4
christopher_jo4Author
New Participant
April 11, 2019

Okay, will be exploring other options based on what I have available. Thanks!

smacdonald2008
smacdonald2008
New Participant
April 11, 2019

Adobe will never comment on future product functionality. Garvav answer is correct for this thread.

Gaurav-Behl
Gaurav-Behl
New Participant
April 9, 2019

Agreed, I certainly think that it would but let a Staff member answer that.

christopher_jo4
christopher_jo4Author
New Participant
April 9, 2019

Thanks gauravb10066713, that is correct and I'm aware of this initial support.

What I'm trying to figure out is if we'll get the enhanced Content Fragment support for the Assets HTTP API in 6.4 in future updates.

To dig into some specific details:

When I create a CF on 6.4 and access it through the Assets API, I get high-level details of the CF like title and description, but none of the actual properties inside the CF itself.

When I create a CF on 6.5 and access it through the Assets API, it also provides a "properties" -> "elements" -> "main" field that I can dig into which shows the critical CF properties I want to grab.

I'm hoping this support will come to 6.4 via updates, but wanted to see if that was on the roadmap or not.

Gaurav-Behl
Gaurav-BehlAccepted solution
New Participant
April 9, 2019

Per my understanding this is already available in 6.4 and would have updated features w.r.t CF and other things in 6.5.  I'm able to access

http://localhost:4502/api/assets/<asset_path>.json and get the listing

e.g. http://localhost:4502/api/assets/we-retail/en/experiences/48-hours-of-wilderness/48-hours-of-wilderness.json

check -

Assets HTTP API

Terms & ConditionsAccessibility statement

Loading footer...