Can we change the default Assets HTTP API Path /api/assets ? | Community
Skip to main content
surenk
August 21, 2020
Solved

Can we change the default Assets HTTP API Path /api/assets ?

  • August 21, 2020
  • 2 replies
  • 1234 views

As listed in the docs https://docs.adobe.com/content/help/en/experience-manager-65/assets/extending/mac-api-assets.html to access assets using API..

  1. https://[hostname]:[port]/api.json
  2. https://[hostname]:[server]/api/assets.json

is there a way to change the path of the default "/api/...." to be something else?

 

Our implementation need to call (external) services that are mapped as https://<server>/api/services  (where <server> is an aem site). 

and when internally calling assets' api's (to access content fragments) in code, we're having issues since they the external and internal api path. 

 

Couple solutions we can.. but can avoid if we can change the path. 

1. Create a servlet to catch `/api/assets` calls and process

2. Add dispatcher rule 

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 AlbinIs1

I don't think so there is any OOTB option to modify the path, but you should be able to map custom URL through Apache/Dispatcher.

Refer the solution explained in the following URL - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/binding-a-servlet-to-a-custom-configured-path/qaq-p/375692

 

Regards

Albin I

www.albinsblog.com

2 replies

AlbinIs1Community AdvisorAccepted solution
Community Advisor
August 21, 2020

I don't think so there is any OOTB option to modify the path, but you should be able to map custom URL through Apache/Dispatcher.

Refer the solution explained in the following URL - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/binding-a-servlet-to-a-custom-configured-path/qaq-p/375692

 

Regards

Albin I

www.albinsblog.com

Singaiah_Chintalapudi
August 21, 2020

Have a different URI and handle them at Apache/Dispatcher to PT (to maintain the same URL) or redirect to /api/*. This would be the easy one for maintenance.

 

To use PT and retain the original URI/URL:

RewriteRule ^your/custom/uri/$ /api/your/path.json [PT]

 

The above would internally redirect the request and the user would not see the redirection on the broswr.

 

You can always redirect the user. Let me know if you want the example.