REST APIs and documentation

b_victor — Tue, 04 Mar 2014 03:03:49 GMT

Hello,I'm integrating with a standalone Alfresco 4.2 from an external client app written in Java. I've had great luck with the CMIS API using OpenCMIS with extensions. I'm having more difficulty figuring out if I'm doing things right for some of my needs, though.Specifically, my app needs to two m

Re: REST APIs and documentation

jpotts — Tue, 04 Mar 2014 21:24:23 GMT

Thanks for reading the tutorial.

When you see a URL that includes "public" that is part of the Public API. You can find documentation on that here:
https://www.alfresco.com/cmis/browser?id=workspace%3A//SpacesStore/b09d212a-00c6-4ec3-9764-0eca67bb8529

When possible, you should use the public API.

As you are finding out, it isn't always possible. So you can go to http://localhost:8080/alfresco/service/index and browse out-of-the-box web scripts. The caution here is that many of those web scripts are not public. They are subject to change without notice.

You can browse web scripts by lifecycle at this URL: http://localhost:8080/alfresco/service/index/lifecycle/

You need to stick to "public_api" and "draft_public_api" if at all possible.

Another approach to consider, and this would work for your people/groups requirement as well as your workflows requirement, is to create your own custom web scripts. Those web script controllers can then use the Alfresco JavaScript API or Alfresco Java API to do what you need to do. The nice thing about that is that you are in full control of the HTTP part of the API and your controllers are using standard API to do what needs to be done.

For this reason, it is recommended that you use the Public API first, custom web scripts second, and then the out-of-the-box web scripts.

Jeff

topic Re: REST APIs and documentation in Alfresco Archive

REST APIs and documentation

Re: REST APIs and documentation