The Latest News On The API Economy
Searching: No Search Term , Filtered By Article Type: "Native Case Study"
In this follow up to a previous case study examining Intuit's Quickbooks ecosystem, we're improving on an existing diagram of the Quickbooks ecosystem; this time we get into the details of what a successful API ecosystem looks like and how you should go about building yours.
In this last installment of our series "The End of the API Economy As We Know It" we look at how DataSift had their licensing agreement with Twitter unexpectedly terminated. This story details how DataSift coped with the setback and provides lessons for any company that relies on third-party APIs.
The Centers for Medicare and Medicaid Services recently faced with the reality that their legacy system, one that processes 4% of the US GDP, needed to be modernized for a number of reasons. This is the story of what USDS is doing to address the situation and keep a mission critical system online.
As part of our series on the end of the API economy as we know it, we offer a story about a company that survived being shut out of the API that was the lifeblood of its business. This is the story of PeopleLinx, a company that made money using the LinkedIn API, until the API access was removed.
This is the third API profile in what we are calling the "Growth Series." HelloSign provides an API that allows developers to create an eSigning experience that's a seamless part of a digital document. This feature along with others has fueled a 10x growth in calls made to its API.
As part of the series on getting the most ROI out of your API, this case study shows how Intercom grew its developer program by tracking key indicators across a range of business goals — platform reach, developer engagement, financial impact — that aligned with their API strategy and business plan.
Today, third party developers are using EHR management APIs to meet the unique needs of customers. They are using rapid application development techniques to create custom client applications that leverage the power of these APIs. drchrono is becoming the API of choice for many of these developers.
Part of our series on getting the most ROI out of your API spotlights the real-life decisions made by providers. Here we show how Dun & Bradstreet maintains and promotes its APIs. See how the company treats its APIs as products, considering them necessary additions that grow in strategic value.
When a business's various stakeholders consider the decisions to make as they execute an API strategy, the API's business model will prove to be key. But as Ziggeo learned, in the interests of seizing the biggest opportunities, you may have to go back on your initial business model decision.
This is the first API profile in what we are calling the "Growth Series." Mapbox provides an API that allows developers to create maps with rich data visualizations by using multiple data layers. This feature along with others has fueled an 11x growth in calls made to its API.
Dixons Carphone is an electrical and telecommunications retailer with an estimated revenue of $15.3 billion annually. This case study looks at how Dixons was able to leverage APIs to reach their business goals, exceed sales and operational targets, and create a whole new product line.
Contentful is a content management service managed via APIs that lets users upload and store content, create web and mobile interfaces and more. This case study looks at how Contentful drove engagement and eventually adoption through the use of SDKs, both official and community contributed.
Edmunds is an automotive research website that offers APIs for developers to access automotive content. This case looks at Edmunds’ focus on encouraging third parties to be viable businesses via the Edmunds APIs. Edmunds also focuses on outreach activities including hosting an accelerator program.
This case study looks at the strategies used by Philips Hue that have seen their developer adoption grow by 157%. A clear understanding of developer personas has helped Philips to know the needs and app development environments of their ecosystem which has fostered better developer relations.
Podio is a SaaS provider that lets customers create their own apps and workflows. This study looks at how Podio has focused on their core business use case by supporting technologies often found in the enterprise and how they launched a marketplace to ease discovery of 3rd party integrations.
SimilarWeb provides website and mobile statistics tracking with the company's API offering access to the data streams of their SaaS offering. This case looks at how SimilarWeb has treated their API with a product perspective allowing them to target new markets of end users outside of developers.
TransportAPI provides open data access to all of Greater London's transport routes via a real-time API. This case study looks at how TransportAPI has identified a broader context for the use of their transport data and leveraged that to steadily grow an API as product business.
Pharmacy and wellness retailer Walgreens offers a photo printing service that can be integrated with via their Photo Prints API. This case study looks at how Walgreens shares key sales trends data and provides discounts that developers can pass onto end users to encourage seasonal photo printing.
WePay is a payment processing company focusing on platform businesses. WePay grew it's API by 600% in 2014 and this case study looks at how this growth was keyed by a refresh of its developer portal, including sample code and tutorials, to refine the messaging towards platform oriented businesses.