Limit Your API Liability with Proper Controls

From a banking perspective, an enterprise API's legal status and accounting procedure can be confusing. With so many people consuming raw publicly open data, sometimes through a 3rd party host, business executives don't know whether to consider an API as a liability or an asset to a company's interests. Potential risks may be mitigated by crafting in-depth customer agreement terms, and when applicable, respecting international data privacy laws.

In order to avoid the pitfalls of public data consumption, such as the recent SnapChat API security failure, Andy Thurai recommends to implement proper clearance controls, filing detailed records on the location of each user. In order to retain data ownership, the data lifecycle must be tracked, stored efficiently, and disposed of in a timely fashion when necessary. 

Original Article

Is your API an asset or a liability?

Bill Doerrfeld I am a consultant that specializes in API economy research & content creation for developer-centric programs. I study Application Programming Interfaces (APIs) and related tech and develop content [eBooks, blogs, whitepapers, graphic design] paired with high-impact publishing strategies. I live and work in Seattle, and spend most of my time as Editor in Chief for Nordic APIs, a blog and knowledge center for API providers. For a time I was a Directory Manager & Associate Editor at ProgrammableWeb, and still add new APIs to the directory every now and then. Drop me a line at bill@doerrfeld.io. Let's connect on Twitter at @DoerrfeldBill, or follow me on LinkedIn.

Comments