In this post, I will provide some detail on using the kippy web APIs, with the example of a recent kippy and Sharepoint integration.

 

I will assume you are familiar with the basic concepts of web APIs. If not, basically, the kippy web APIs are a secure and simple way to get to your information to and from kippy from your systems. Sharepoint is a popular enterprise collaboration and document management system - but for the purpose of this post, simply represents any system in your organisation.

 

First, let's set the context:

 

A medium-to-large sized global organisation wanted to use kippy to model and maintain their strategy and performance data. So they sent over their existing data held in spreadsheets and within a few days it was uploaded into kippy. This allowed all the appropriate people in that organisation to now contribute and collaborate on that info - securely via their browser, rather than by emailing around Excel spreadsheets.

 

Next, they wanted to augment their internal collaboration portal, to use, display and join that information with other internal systems.

​