Getting started with an open API initiative
When CGAP asked digital finance executives about the number one piece of advice they would give to another provider getting started with open APIs, Hover CEO Ben Lyon emphasized that APIs are not just a product, they’re a “standalone business.” Open APIs can benefit providers in many ways, as documented in CGAP’s case studies, but successfully implementing a API initiative requires a business strategy, new company processes, and investments in technology and customer engagement. CGAP created the resources below to help providers in emerging markets better understand and navigate key considerations when implementing an open API initiative.
What are the key elements of an open API strategy?
While it is important to take a strategic approach to open APIs, you do not need a full-fledged strategy in place to get started. It is better to start small, offering a limited number of APIs to existing partners, learning about developers’ needs, and testing business models, before evolving toward a full open strategy.
How should open API products be priced?
Pricing is a key component of any open API strategy. A pricing strategy should do at least three things: (1) help the financial services provider achieve specific business objectives, (2) generate business value for each target API consumer segment, and (3) align with market expectations and norms for pricing.
How can I select the right technology stack for open APIs?
One of the most important factors in implementing an open API strategy is selecting the right technology solutions. A common mistake among business leaders is to focus on the business strategy without engaging on key technology decisions. This can lead to technically unreliable solutions, the need for ongoing technical support to third-party API consumers, or a need to manage financial risk when things go wrong.
What risks do open APIs pose to my business, and how can I mitigate them?
When financial services providers enable developers to leverage their data and capabilities in third-party products, they assume certain risks. The most common risks include unauthorized transactions on customer accounts, misuse or exposure of customer data, and reputational issues stemming from association with third parties, especially when initiatives are co-branded. These risks can be mitigated through sound legal contracts and other measures.
Here are three design principles that financial services providers should keep in mind when making technology decisions related to their open API products.
Photo: Simone D. McCourtie, World Bank
CGAP engaged law firm Hogan Lovells to produce this in-depth guidance for providers on how to mitigate risk with open APIs. It includes a template for legal contracts with third-party API consumers.
How can I entice third-party developers to use my open APIs in innovative products?
When launching open APIs, do not assume that developers will automatically start using them. To ensure developers are aware of your APIs and drive usage, providers need a go-to-market strategy. It is also important to create resources that make it easy for developers to see the potential applications of the APIs and to start using them. Such resources include an online developer portal and supporting documentation.
