Overview
Submissions are the core resource for creating insurance policies in AI Insurance. A submission contains all the policy information, covered insureds, and configuration needed to generate quotes and bind policies. Key Concepts:- Submissions contain policy-level data and multiple insureds
- Configuration defines available rating fields and coverage types
- ImportPolicy structure represents the policy being submitted
- ImportInsured structures represent each covered entity
API Endpoints
- List Submissions - Retrieve submissions for your company
- Create Submission - Create a new submission with policy and insureds
- Update Submission - Update an existing submission
Using Configuration Response in Submissions and Quotes API
Below we have an example configuration JSON. Configuration files may be very long, so saving the configuration to a file viewer will be very helpful. As noted above, each configuration will have 4 objects:ratingEngineFieldsnonRatingFieldsinsuredEntityTypesenabledCoverageTypes
Configuration Object
ratingEngineFields
TheratingEngineFields object is an array consisting of several child objects.
Each child object contains a fieldId, entityType, companyId, and object field.
Each object in the array represents rating data that can be added to submissions, based on the entityType.
Child objects with the entityType policies can be added to the ratingData dictionary in the ImportPolicy object.
All other child objects can be added to the applicationData dictionary in a [ImportInsured(/api-reference/data-models#importinsured-object)] object.
| Key | Type | Description |
|---|---|---|
fieldId | string (UUID) | Unique identifier for the rating field |
entityType | enum | The type of the rating field. Will be of type policies or one of insuredEntityTypes |
companyId | string (UUID) | Unique identifier for the current company |
field | dictionary | An object representing different types of metadata |
ratingEngineFields Object
nonRatingFields
ThenonRatingFields object is a dictionary with the sub-dictionaries policies, insureds, and events within it. Each sub-dictionary is structured similarly to ratingEngineFields.
However, the entityType of each child object in a sub-dictionary will be the same value as the key of the sub-dictionary. So any child object within the policies sub-dictionary will have entityType = "policies".
Object data from the policies sub-dictionary can be added to the policyCompanyEntityFields dictionary in the ImportPolicy object.
Object data from the insureds and events sub-dictionaries can be added to the insuredCompanyEntityFields dictionary of an ImportInsured object.
| Key | Type | Description |
|---|---|---|
policies | dictionary | A dictionary where entityType = "policies" |
insureds | dictionary | A dictionary where entityType = "insureds" |
events | dictionary | A dictionary where entityType = "events" |
nonRatingFields Object
insuredEntityTypes
TheinsuredEntityTypes object is a dictionary containing sub-dictionaries. These sub-dictionaries are defined based on your configuration but all have the same schema.
insured sub-dictionary schema
entityType which may be referenced by one or more ratingEngineFields objects.
enabledCoverageTypes
TheenabledCoverageTypes object is a dictionary containing sub-dictionaries. These sub-dictionaries are defined based on your configration but all have the same schema.
coverage sub-dictionary schema
name can be used as coverageTypeId in a ImportPolicyCoverage child object.
