I don't think that is documented in a single place at this point. I do think we could start to put that together by reverse engineering the documentation that does exist and the node sdk pieces that are responsible for generation of the Jive specific configuration files. After that the rest is really just a REST model. Still it would be nice if it were a specification that was a bit easier to follow from a single source.
1 person found this helpful
I would definitely start with this document:
Jive Platform - Developer Resources but specifically ...
This document outlines the service exchanges necessary for a service to integrate with Jive as an add-on.