APIs are as vast and varied as the systems that depend on them; while some systems may handle client data, payments, and collaborative research, other APIs may handle less important data such as social media and image sharing.
Due to the variations in application and usage, APIs face a unique set of considerations and issues arising from their availability that no other system faces – the difference between having an API for public consumption or one intended for internal use, in certain circumstances, can mean the difference between megalithic success and catastrophic failure. Read more
Over the last week we followed the API blogosphere discussion surrounding API nomenclature. Steven Willmott does a good job of summing up the recent debate in a 3Scale post, Public Vs. Private APIs.
Interesting timing… we have been compiling an eBook that not only defines a taxonomy for API types but offers insightful business strategies for each variation. Read more
APIs are like LEGO building blocks, it is often said. Many API talks start off by explaining that APIs are like these bricks. They can be combined in innovative and creative ways beyond their originally intended purpose. What are APIs like for LEGO though? Read more
Developer teams from across Finland arrived — often with a colleague or two from their business development unit — to Helsinki’s Skandic Park Hotel on Wednesday for the latest in the Nordic APIs “Private, Public and Partner APIs” event series. Read more
The mood was high, the wraps were eaten, and the coffee was free-flowing: Nordic APIs began its four country tour in Stockholm yesterday with a networking lunch, a packed agenda, and a fully booked room of participants. While there were a handful of business developers in the audience, the bulk of those attending our Stockholm event at city tech hub, Start-up People of Sweden, were developers responsible for designing and deploying APIs within their businesses. Read more