Is your API an asset or a liability?

This article was originally published on VentureBeat.

A touchy API topic is data ownership and liability, regardless of whether the APIs are open or protected. Obviously, depending on your business model and needs, you will choose to expose the APIs and the underlying assets to your developers, partners, public developers, your consumers, or others that I am forgetting. While almost everyone talks about the API business relationships, the liability concern brings the legal relationship to the forefront.

[Image courtsey: jasonlove.com]

liabilityAPIs are considered a contract between the data supplier (or API provider) and the app provider. If you have different API providers that publish APIs from a central place, and multiple third parties use that API catalog to build apps for their consumers (end users), then it becomes complicated. While you can fix some of this by writing detailed contracts and making the app providers and end customers agree to the terms of usability before they use those APIs, as a provider, you are also responsible for implementing controls around your APIs to mitigate most, if not all, of the risks involved.

Read more of this post

Advertisements

Are Public APIs Going Away?

This article was originally published on LinkedIn Pulse.

You might have noticed in the news recently that ESPN has shut down its public API program. According to ESPN, they are trying to “better align their engineering resources with their core product development,” though the actual reason seems to be that they want better control over their unique and licensed content, and better monetization, which public APIs may not offer.

Read more of this post

%d bloggers like this: