Understanding and Leveraging Dais API Integration

Introduction

Dais API Integration offers a simplified yet comprehensive interface for carriers and MGAs to design, host, and enhance their insurance products. This technical article seeks to elaborate on the Connectivity 2.0 features of Dais including the Dais API Integration Workflow and the exciting new Conversational API Integrations updates.

Dais API Integration Flow Overview

Dais supports a seamless integration flow with other external systems. This primarily follows a sequence, constituted of events called "Actions". These actions trigger specific outcomes, providing both internal and external communication. The sequence diagram below illustrates the automated Dais API Integration calling and responding flow that can run simultaneously and asynchronously.

Sequence diagram

In this flow, the event "TRIGGER_FIRED" denotes the beginning of an activity in the Dais system while "TRIGGER_RESPONSE" signifies the end of mentioned activity. The "ACTION_EXECUTION" event happens when Dais dispatches an order to an Action, like calling an external system's API. In the event execution phase, messages are exchanged between the external system and the Dais platform. The "EXTERNAL_OUTBOUND" means Dais requested data from an external system, and "EXTERNAL_INBOUND" symbolizes the response from the external system to the Dais system.

Actions

In Dais, Actions refer to specific functions programmed to respond to events. Actions can be used to talk to an existing system, an external service, or even another part of Dais. An action can be anything like sending an email, calling an external API, creating an activity, and more. Simply put, Actions are packaged functions that perform specific tasks when triggered by events within the Dais system.

Introducing Conversational API Integrations

Our latest release introduces an advanced feature set that enhances the integration between Dais, other systems, and its version of Actions.

Multi-step, bidirectional API integrations allows for complex, multi-step conversations between systems and user-configurable integrations.
Payload shaping capability allows configuration of interaction with remote systems, eliminating the need for custom code.
Select from Three Modes of Integration - pass-through, custom object model, and multi-step as per need.
Event Tags as Action Triggers add an extra level of customization by using tags as filters to decide which actions get triggered for an event.
Dais also offers Vertical-specific Integrations with preloaded and customizable integrations designed for specific industry segments.
Lastly, expansion in Versatile Plugins allows extraction of data from the event anywhere within its ecosystem.

Taking it a step further, this new feature sets the stage for AI-Powered Experiments and interactions. It allows new possibilities like using AI to assess customer risk or qualify leads without requiring an event as a trigger.

In conclusion, the Dais platform's latest API and integration updates provide an enhanced user experience that offers increased control, customization, usability, and integration.