/alfresco/api versus /alfresco/slingshot

cancel
Showing results for 
Search instead for 
Did you mean: 
lngtai001
Member II

/alfresco/api versus /alfresco/slingshot

We upgraded from Alfresco 4.2.2 to Alfresco 5.1.1.

Our "view in browser" links went from http://<hostname>:<port>/share/proxy/api/node

to http://<hostname>:<port>/share/proxy/slingshot/node

we can still use either link.

Why did it change? What is the difference?

We have third party apps that resolve links but cannot resolve the slingshot links which is why I am asking.

2 Replies
afaust
Master

Re: /alfresco/api versus /alfresco/slingshot

Alfresco has made a couple of efforts to better distinguish "public APIs" that should be safe for integration with external applications, and "internal APIs" that only exist to be used via Alfresco Share. "slingshot" is the historic, low-level project name for Share, and anything that is related to "slingshot" should be considered "internal API", which might change without notice from one version to another, and is thus not safe for integrations.

For Alfresco 5.1. you can read about the public ReST API in the documentation. With Alfresco 5.2 they have introduced a formal v1 ReST API.

jpotts
Advanced II

Re: /alfresco/api versus /alfresco/slingshot

Some web scripts have a "lifecycle" that indicates whether they are internal, draft public, or public. I agree with Axel that you should avoid using any of the slingshot URLs. But you should also get in the habit of checking that lifecycle so that you don't inadvertently use an internal API regardless of whether it is "slingshot" or not.