Extending CS REST API
I'm currently digging into the REST API ospaces but does Open Text publish any sort of best practices and/or how-to guide for extending the REST API? I can envision a few scenarios where you might want to expose other CS entities to the API which are not nodes (i.e. assignments, tasks) or nodes that you want to have specific functionality for (i.e. projects, forms). Obviously I would be sensitive about exposing Live Reports unless those are put through a proper change management process (as we had when I was at Suncor).
I can probably find my way around the builder to determine an approach if I were to extend REST API, but was looking to see if anything was already published.
-Hugh
Comments
-
Hi Hugh,
Please see the "Content Server REST API - Quick Start Guide" located on this site. Search for this text and you should find it easily.
0
Categories
- All Categories
- 108 Developer Announcements
- 53 Articles
- 106 General Questions
- 144 IM Services
- 43 OpenText Hackathon
- 32 Developer Tools
- 20.6K Analytics
- 4.1K AppWorks
- 8.9K Extended ECM
- 899 Cloud Fax and Notifications
- 77 Digital Asset Management
- 9.3K Documentum
- 29 eDOCS
- 120 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management