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

Tagged:

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.

  • Thanks Chris,
    I went and used that guide. It took a bit of time to understand what you guys were getting at with the map structure but I got my first REST API extension working.
    -Hugh