differences between apis used by rdme client and apis documented in readme reference

[akil-rails]

When adding a doc:

1. As per the rdme client the request includes lastUpdatedHash , while the api reference has no documented provision for this.

When fetching all docs for a category

1. As per the rdme client, the response includes lastUpdatedHash which is used to compare, while the api refernce does not return this attribute.

When adding an API

1. As per the rdme client, the api is added to the registry, but this api is not documented in the api reference. Instead what is published is create api specification which does not return the registryUUID, and also creates categories/pages etc in addition to adding to the registry.

Are these differences intentional ? We have our own pipeline (java based) and don't want to introduce node (even via docker) .