Guides
- Quickstart
- Axle Ignition
- Axle for Platforms
- Monitoring
- Sandbox
API Reference
- Overview
- Ignition
- Tokens
- Accounts
- Policies
- Carriers
- Platform
- Sandbox
Coverages
This page provides additional detail about the Axle Schema’s insurance coverage types and highlights key rules and checks used to ensure accurate data. Coverages are provided through the coverages
array in Policy objects.
Rules applied to all coverages:
- If both the
limitPerAccident
andlimitPerPerson
values are provided for a coverage, thelimitPerAccident
value must be greater than thelimitPerPerson
value. - If a specified coverage is afforded to all properties on the policy, the
property
field will beundefined
.
For standardization purposes, Axle performs opinionated data transformation of insurance carriers’ data into the Axle Schema. As a result, Axle makes certain carrier enumeration inferences to map carrier data into the Axle Schema.
Auto Policy Coverage Types
Rules applied:
- If the carrier returns limits combined as
“$50,000 / $100,000”
, the first value representslimitPerPerson
and the second value representslimitPerAccident
. If there is only a single limit returned, the limit will be recorded aslimitPerAccident
. - If the policy returns a combined single limit (CSL) for Bodily Injury and Property Damage, the limit will be set as
limitPerAccident
for both Bodily Injury and Property Damage coverages.
Suppression checks:
limitPerAccident
,limitPerPerson
, anddeductible
fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.
Fields
BI
Bodily Injury
Rules applied:
- If the carrier returns limits combined as
“$50,000 / $500”
, the first value representslimitPerAccident
and the second value represents thedeductible
. - If the policy returns a combined single limit (CSL) for Bodily Injury and Property Damage, the limit will be set as
limitPerAccident
for both Bodily Injury and Property Damage coverages.
Suppression checks:
limitPerAccident
anddeductible
fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.
Fields
PD
Property Damage
Rules applied:
- If the carrier returns limits combined as
“$50,000 / $100,000”
, the first value representslimitPerPerson
and the second value representslimitPerAccident
. If there is only a single limit returned, the limit will be recorded aslimitPerAccident
. - If the policy returns a combined single limit (CSL) for Uninsured Motorists Bodily Injury and Uninsured Motorists Property Damage, the limit will be set as
limitPerAccident
for both Uninsured Motorists Bodily Injury and Uninsured Motorists Property Damage coverages andlimitPerPerson
will beundefined
.
Suppression checks:
limitPerAccident
andlimitPerPerson
fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.
Fields
UMBI
Uninsured Motorists Bodily Injury
Rules applied:
- If the carrier returns limits combined as
“$50,000 / $500”
, the first value representslimitPerAccident
and the second value represents thedeductible
. - If the policy returns a combined single limit (CSL) for Uninsured Motorists Bodily Injury and Uninsured Motorists Property Damage, the limit will be set as
limitPerAccident
for both Uninsured Motorists Bodily Injury and Uninsured Motorists Property Damage coverages andlimitPerPerson
will beundefined
.
Suppression checks:
limitPerAccident
anddeductible
fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.
Fields
UMPD
Uninsured Motorists Property Damage
Rules applied:
- If the carrier returns limits combined as
“$50,000 / $100,000”
, the first value representslimitPerPerson
and the second value representslimitPerAccident
. If there is only a single limit returned, the limit will be recorded aslimitPerAccident
.
Suppression checks:
limitPerAccident
andlimitPerPerson
fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.
Fields
UIMBI
Underinsured Motorists Bodily Injury
Rules applied:
- If the carrier returns limits combined as
“$50,000 / $500”
, the first value representslimitPerAccident
and the second value represents thedeductible
.
Suppression checks:
limitPerAccident
anddeductible
fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.
Fields
UIMPD
Underinsured Motorists Property Damage
Rules applied:
- If the carrier returns limits combined as
“$50,000 / $100,000”
, the first value representslimitPerPerson
and the second value representslimitPerAccident
. If there is only a single limit returned, the limit will be recorded aslimitPerAccident
.
Suppression checks:
limitPerAccident
andlimitPerPerson
fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.
Fields
UUIMBI
Uninsured & Underinsured Motorists Bodily Injury
Rules applied:
- If the carrier returns limits combined as
“$50,000 / $500”
, the first value representslimitPerAccident
and the second value represents thedeductible
.
Suppression checks:
limitPerAccident
anddeductible
fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.
Fields
UUIMPD
Uninsured & Underinsured Motorists Property Damage
Suppression checks:
limitPerAccident
anddeductible
fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.
Fields
COMP
Comprehensive
Home Policy Coverage Types
Rules applied:
- When the deductible is listed differently based on the type of claim, the deductible associated with covered perils will be returned. This deductible value is often represented as “All Perils”, “All Covered Perils”, or “Other Covered Perils”.
Suppression checks:
- If both the policy
premium
and Dwelling coveragelimitPerAccident
values are defined, the Axle Service will ensure that the premium-to-Dwelling-limitPerAccident ratio falls within our set bounds of reasonability. If this ratio is greater than our upper bound, both the policypremium
and Dwelling coveragelimitPerAccident
values will be conservatively set tonull
. If apremium
value exists but no DwellinglimitPerAccident
value is present, then thepremium
will be conservatively set tonull
. limitPerAccident
anddeductible
fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.
Fields
DW
Dwelling
Rules applied:
- When the deductible is listed differently based on the type of claim, the deductible associated with covered perils will be returned. This deductible value is often represented as “All Perils”, “All Covered Perils”, or “Other Covered Perils”.
Suppression checks:
limitPerAccident
anddeductible
fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.
Fields
OS
Other Structures
Rules applied:
- When the deductible is listed differently based on the type of claim, the deductible associated with covered perils will be returned. This deductible value is often represented as “All Perils”, “All Covered Perils”, or “Other Covered Perils”.
Suppression checks:
limitPerAccident
anddeductible
fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.
Fields
PP
Personal Property
Rules applied:
- When the deductible is listed differently based on the type of claim, the deductible associated with covered perils will be returned. This deductible value is often represented as “All Perils”, “All Covered Perils”, or “Other Covered Perils”.
Suppression checks:
limitPerAccident
anddeductible
fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.
Fields
LOU
Loss of Use
Rules applied:
- Only a
limitPerAccident
orlimitPerPerson
value can exist on this coverage but not both.
Suppression checks:
limitPerAccident
anddeductible
fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.
Fields
MED
Medical Expenses