February 16, 2021
Making Inroads With Open APIs
Insurers must allow third parties to access their data and products and be present – and relevant – in customers’ digital ecosystems.
Open insurance is about sharing vast and ever-growing volumes of structured data in a digital ecosystem to stimulate the creation of innovative insurance-related propositions for consumers. When customers are made the focal point of new digital business models, new opportunities continuously arise for cross-sectoral partnerships, platforms or collaborative efforts.
This means that it is crucial for insurance companies to allow third parties (e.g. banks, fintech, aggregators, mobility providers, etc.) to access their data, products and services, and also for them to be present – and relevant – in their customers’ digital ecosystems. Like open banking, open insurance initiatives drive API-enabled access to insurance data, products and services.
The Open Insurance Monitor presents how the insurance industry is developing towards open APIs
A rich API portfolio supports the best service provision toward customers and partners within third-party platforms. It is also important for insurers to offer a good developer experience to create the optimal environment for collaborative partnerships and innovation. INNOPAY, a consultancy, has launched the Open Insurance Monitor (OIM) to continuously measure and benchmark this functional scope of APIs and developer experience offered in the insurance landscape (see figure 1). OIM considers organizations around the world that publish insurance APIs via developer portals, including insurers, insurtechs and banks.
Three key insights from the Open Insurance Monitor
1. Lack of focus on developer experience
The OIM reveals that insurers’ first efforts are mostly aimed at establishing a rich API portfolio with insurance-related functionality, with minimal focus on the developer experience.
The top left corner of Figure 2 shows several insurers leading the way as innovators of functionality. AXA offers a wide variety of functionality in most components of the insurance value chain and for multiple types of insurance products. These services include quoting and selling insurance, claims management and service-provider support during the execution of services to clients. Cover Genius also offers services in multiple components of the value chain, including services for product origination as well as claims management. Health insurer Humana provides a wide variety of API services such as enrollment in medical care programs, retrieval of medical information and supporting functionality for medical professionals during the execution of services.
Analysis reveals that insurers are still only in the early stages in terms of creating the developer experience. Although most insurers have taken initial steps in providing API documentation, there is a strong focus on the technical aspect or specifications of APIs. The developer experience could often be further improved by increasing developer usability (e.g. tools, tutorials) and engaging with the community to spur collaboration and innovation.
See also: Designing a Digital Insurance Ecosystem
2. Banks are making inroads, too
Unsurprisingly, the banks included in the OIM offer a more advanced developer experience due to their open banking efforts and investments. Extending their API portfolios with insurance services would further boost their bancassurance models.
The OIM identified a small group of banks that offer insurance services through APIs. This is the next wave of bancassurance and is an interesting revenue model for open banking. Thanks to their open banking capabilities, the banks included all have a solid basis in terms of API documentation and developer usability. Standard Chartered sets itself apart through features for community development such as regularly posting news articles and organizing hackathons and other types of events. OCBC emerges as a good all-round player in all components of developer experience, while Citi stands out in terms of developer usability by supporting fast onboarding and providing instruction guides for calling APIs, authentication and the sandbox environment. However, the scope of insurance-related functionality at these banks is still limited. If they decide to extend their API portfolios with related services, they will move toward becoming masters in openness, which will boost their bancassurance models.
3. Insurers are lagging behind in openness
Benchmarking against the masters in openness (e.g., National Bank of Greece and Deutsche Bank) reveals that insurers still have a long way to go in terms of openness. In fact, out of all the parties analyzed, only one is currently a master in openness: the U.S.-based insurance company Nationwide, thanks to offering a variety of insurance APIs plus enhancing the developer experience through clear documentation and good developer usability.
Nationwide’s extensive API portfolio currently consists of a variety of services for information retrieval, insurance quoting and issuing policies as well as APIs aimed at policy servicing. Portfolio extension could be achieved by including API services for managing claims and supporting service providers. Besides providing clear technical API documentation, Nationwide sets itself apart from other developer portals by emphasizing the business potential of its APIs through feature display and use cases, as well as offering good developer usability.
No overall winner
As with open banking, there is currently no overall winner in the open insurance landscape based on the developer portal capability model, as depicted in Figure 3.
See also: 2021: The Great Reset in Insurance
For more details on the monitor and how to get access to digital ecosystems, please visit the website.