Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

REST API to Create Folder in DAM is not working as documented

jonasy18481676
Level 2
Level 2

I'm communicating with Adobe Experience Manager, Version 6.5.6.0. I'm trying to create a folder using the HTTP REST API.

 

The documentation here:

https://experienceleague.adobe.com/docs/experience-manager-65/assets/extending/mac-api-assets.html?l...

Mentions:

  • POST /api/assets/myFolder -H"Content-Type: application/json" -d '{"class":"assetFolder","properties":{"title":"My Folder"}}'
  • POST /api/assets/* -F"name=myfolder" -F"title=My Folder"

However, when I create a folder like this:
postman test.png

Then I get a created answer, but it only uses the name I've provided, not the title. This is a screenshot of the created folder:
created folder.png

 

And this is a screenshot of the properties of that created folder.folder properties.png

 

Why doesn't it use the folder title I've configured in the POST request? Am I doing something wrong?

1 Accepted Solution
kishorekumar14
Correct answer by
Level 10
Level 10

Hi @jonasy18481676 ,

 

Instead of title KEY in body, Please try with jcr:title. It works.

 

Postman

 

kishorekumar14_0-1633769194233.png

 

AEM

 

kishorekumar14_1-1633769305068.png

 

View solution in original post

4 Replies
kishorekumar14
Correct answer by
Level 10
Level 10

Hi @jonasy18481676 ,

 

Instead of title KEY in body, Please try with jcr:title. It works.

 

Postman

 

kishorekumar14_0-1633769194233.png

 

AEM

 

kishorekumar14_1-1633769305068.png

 

View solution in original post

jonasy18481676
Level 2
Level 2

Hi @kishorekumar14 ,

 

Thanks! That indeed works.

 

I usually try to avoid functionality if it is different to what is documented to be sure that the functionality will keep working in future versions. Do you know the reason that the documentation is not correct? Will it continue to work in future versions?