API Factory, Marketplace, or Embedded Experience for Insurance-as-a-Service

Create a vendor selection project
Click to express your interest in this report
Indication of coverage against your requirements
A subscription is required to activate this feature. Contact us for more info.
Celent have reviewed this profile and believe it to be accurate.
We are waiting for the vendor to publish their solution profile. Contact us or request the RFX.
Projects allow you to export Registered Vendor details and survey responses for analysis outside of Marsh CND. Please refer to the Marsh CND User Guide for detailed instructions.
Download Registered Vendor Survey responses as PDF
Contact vendor directly with specific questions (ie. pricing, capacity, etc)
17 August 2021


Application programming interface (API) has been the go-to solution when insurers and technology vendors discuss the way to develop, package, and ship function in a scalable modular manner. Going forward, the next-generation insurer will require capabilities to integrate legacy functions with modern technologies such as AI/ML functions for customer onboarding or predictive analytics.

This raise the following questions that we will address in this report:

1. What are the API business models observed in recent implementations or discussions?

2. How can participants in the insurance ecosystem benefit and design their strategy to benefit the most from the API model?

In this report, we will examine the common API model in today's insurance technology stack. We will understand from insurtechs' and technology vendors' approaches to modernizing legacy infrastructure with modern functionalities or offering new insurance distribution model. This will lead to a discussion about API factory versus embedded insurance. Read on to discover how we identify and illustrate the below two models of providing API services for the insurance ecosystem.