We are sometimes asked (usually by our more techie users) whether Kerika has a published API.

The short answer is “No”; the longer answer is “Not yet.”

We do have a server API, of course, that the Kerika front-end client application itself uses, but it is a very proprietary and non-standard API at present.

This is largely because of an early decision we made to use CometD for our real-time client-server communications.

CometD is a form of a long-poll architecture, but our implementation, unfortunately, is not very standard, in part because we built an “API generator” a long time ago that allows us to create new APIs fairly quickly using metadata descriptions of the desired features.

This was helpful when we were first getting started, but, quite honestly, it isn’t an approach that makes a lot of sense any more and we have migrated away from using that API generator.

But, because of our history/legacy code, we currently have a mix of auto-generated APIs and newer API, and this isn’t really something that we want to publish and support for external third-party development.

We plan to redo our API this year to make it more standard and easier for third-party developers to use, at which point we will publish it and start encouraging more platform development around Kerika.