Description of problem: I think that REST API should be built according some rules. I've found good example of rules which can be reused and extended/modified for RHSCon: https://github.com/ManageIQ/manageiq_docs/blob/master/api/overview/http.adoc Similar specification for authentication: https://github.com/ManageIQ/manageiq_docs/blob/master/api/overview/auth.adoc I think that rules for RHSCon should be also documented in documentation.
I still think that for example return codes should be unified among all functions in API. But we can only document rules according API is built. --> documentation
Moving to core component, because the API documentation needs to be part of upstream repository directly written by developers. Anjana is not going to fully document the API including few basic examples based on the source code.
Upstream issue: https://github.com/skyrings/skyring/issues/13