What APIs and API features will deliver value, and to whom? What APIs are available or needed? What are the API developers’ needs?

Are you an API Consumer or an API Provider and how does that affect your business strategy? What do we need to think about when designing an API? Who else would be able to use this API with the same value proposition?

What happens to the business if the API is unavailable? What if there is a data breach or incorrect data or functionality? Does someone die, or is it only a PR disaster? How you can mitigate the risk?

Discover legal and geopolitical requirements and considerations as well as integration architecture and network requirements.

How much and how often does your API usage peak?

What data should the API use? How will the API work? What standards and formats do we need? How can non-API experts take part in API designing?

How should endpoints i.e. the resources that our API allows the API consumers to use, be named? What features and thus endpoints should be included in the same API? To version or not and how?

Use this checklist to audit your API prototype or a ready made API before publishing it to stakeholders, or, why not before buying an API

One of the fundamental challenges in IoT projects is that various IT specialists, device experts, platform providers, and business experts often fail to understand one another – or, more precisely, the implications of each other's domains on their own. In the realm of IoT, business expertise encapsulates all areas where IoT is utilised.