# GIMO Platform APIs

General Insurance Service (GIMO) provides you with a set of granular platform APIs. You can embark on journeys in various forms with applications built around those APIs.

This guide introduces APIs on GIMO and related concepts that you need to understand before using those APIs.

## Insurance-specific APIs 

GIMO offers insurance-specific microservices and APIs that enable a wide range of digital insurance journeys. There are more than 1,000 insurance APIs across 9 domains, including Policy Administration (PA), Claims, Sales Channels, and Parties. These APIs are designed to support both traditional user journeys and digital business flows. Each domain contains multiple microservices, each of them has a set of atomic and accelerator APIs.

## Related Concepts 

 * **Atomic APIs**

Atomic APIs are used in fundamental transaction scenarios of insurance business in different domains.     
It takes some steps (namely a series of internal updates and computation) to carry out insurance transactions such as Policy Issuance and Claim Adjudication. Atomic APIs provide developers with the necessary tools and functionalities to handle these tasks in a granular and detailed manner.

 * **Business APIs**   
Business APIs are the combination of specific atomic proposal APIs. They are designed to further reduce the development efforts and facilitate the creation of specific processing flows, particularly for those required in digital businesses.

 * **Private Business Object Data**  
 Although GIMO supports various business objects, including Policy, Claims, and Customers, business object data is private and can only be accessed through APIs.

 * **JSON Object Models**     
GIMO’s Data Dictionary (DD) contains over 235 predefined data models, such as **PolicyCustomer**, **ClaimSettlement** and **SalesLicense**. These predefined data models are mapped to platform fields. When using insurance APIs, you can define JSON models for business objects in the DD. The JSON requests for such APIs include a subset of fields. In other words, they do not have to cover the entire object model. However, if there are mandatory fields or sections, they need to be included in every request.    
The following guides provide more information on predefined and product-specific data models on GIMO, as well as how to maintain and update these object models and derive a payload for Policy API requests:  
    - Data Dictionary Concepts  
    - [Create the Data Model for Technical Product](https://docs.insuremo.com/gi_product_design/product_cfg_operation#7create-the-data-model-for-technical-product1)
    - [Generating Policy API Request Payload](https://docs.insuremo.com/gi_product_design/product_cfg_operation#8generating-policy-api-request-payload1)
    
 * **API Orchestration**  
When building applications that require access to or updating of data for multiple business objects, you can create an API orchestration by integrating platform APIs for those objects.   
Take Policy Issuance as an example:  
![GIMO_API_0](image/api_concept/GIMO_API_0.png)   
The diagram illustrates how frontend API orchestration can be created around platform APIs to perform actions on different business objects.

 * **Product Configuration**  
To use the Proposal, Policy, and Endorsement APIs, you need to have knowledge of product configuration and policy models.

## GI Policy API Documentation

User can go to [InsureMo API Documentation](https://docs.insuremo.com/tech/pro/sdk/api) to view all the API documentation for details.

For GI Policy APIs, please specifically refer to below categories:

* [Proposal](https://docs.insuremo.com/tech/pro/sdk/api/proposal)
* [Endorsement](https://docs.insuremo.com/tech/pro/sdk/api/endorsement)
* [Quotation](https://docs.insuremo.com/tech/pro/sdk/api/quotation)
* [Policy](https://docs.insuremo.com/tech/pro/sdk/api/policy)

## What's Next

 * Read the GIMO Platform API Reference Guide to learn more about the different API domains and functions on GIMO. 
 * Start using GIMO Platform APIs to create various policy issuance journeys.