Manage Locations

Manage location data using Risk Modeler API services

Overview

A location is a property, building, business, or other asset that may be damaged by catastrophe events. When location coverage is applied to a location, that location is known as a location exposure.

Every location is defined by a set of location attributes (for example, property, address, postalCode) and optional building attributes, reinsurance cessions, peril attributes (earthquakes, floods, fires, etc.), and other attributes.

Location coverage defines the liability of the underwriter for damages to entities (buildings, building contents, businesses) at a specific location due to catastrophe events. A location is generally tied to a specific account, which identifies the relevant cedants, underwriters, and policies.

In this procedure, you will create a new location object that is linked to an account and define coverage for that location.

Add locations

The POST locations resource enables you to create new locations and add that object to a specific EDM data source. The name of the datasource must be specified as a query in the endpoint.

All other parameters are specified in the body of the request. The location may be defined by mandatory location attributes (property, address) and optional building attributes, reinsurance cessions, and peril attributes (earthquakes, floods, fires, etc.) associated with the site.

curl --location --request POST 'https://{host}/riskmodeler/v1/locations/?datasource=postman_edm' \
--header 'Content-Type: application/json' \
--header 'Authorization: {api_key}' \
--header 'Content-Type: application/json' \
--data-raw '{
    "property": {
  "locationName": "LowRes location",
  "yearBuilt": 1949,
  "floorOccupancy": "",
  "rentalPropertyIdentifier": {
"id": 0,
"name": ""
  },
  "buildingClass": {
"code": 2,
"name": "2 - Light Metal"
  },
  "isPrimaryBldg": true,
  "occupancyType": {
"id": 17,
"name": "17 - High Technology"
  },
  "accountId": 5,
  "buildingClassScheme": {
"code": "ATC",
"name": "ATC"
  },
  "nship": null,
  "userGroundElev": -999,
  "slope": null,
  "heightUnit": {
"id": 2,
"name": ""
  },
  "floodDefHtAboveGrnd": -999,
  "occupancyTypeScheme": {
"code": "ATC",
"name": ""
  },
  "expireDate": "9999-12-31T08:00:00.000Z",
  "areaUnit": {
"id": 2,
"name": ""
  },
  "siteName": {
"code": "",
"name": "Golden Gateway Apts"
  },
  "stories": 4
  "mfdSubcategory": {
"id": 0,
"name": ""
  },
  "bldgHeight": null,
  "userBfe": -999,
  "huZone": {
"code": "B",
"name": ""
  },
  "floorArea": 1452.0,
  "inceptDate": "9999-12-31T08:00:00.000Z",
  "floodDefenseElevation": -999,
  "contentLossTrigger": {
"id": "",
"name": ""
  },
  "otherZone": "",
  "locationNumber": "1",
  "floodDefenseElevationUnit": {
"id": 2,
"name": ""
  },
  "buildings": 1,
  "dwellTime": null,
  "useContentValue": {
"id": "",
"name": ""
  }
    },
    "address": {
  "geoResolutionCode": {
"id": 5,
"code": "",
"name": "ZIP Code"
  },
  "latitude": 37.796469
  "admin1Name": "",
  "block": "",
  "addressType": {
"id": 1,
"name": ""
  },
  "admin2Name": "SAN FRANCISCO COUNTY",
  "longitude": -122.399317,
  "countryRmsCode": "US",
  "admin3Name": "FILLMORE",
  "admin1Code": "CA",
  "admin4Name": "",
  "admin2Code": "071",
  "streetAddress": "185 Jackson Street",
  "admin3Code": "0716",
  "blockGroup": "",
  "cityName": "California",
  "country": {
"code": "US",
"name": "United States"
  },
  "postalCode": "94111",
  "cityCode": "14",
  "countryScheme": "ISO2A"
    },
    "currency": {
  "code": "USD",
  "name": "US Dollar"
    }
}'

In this example, you defined the address and property objects. These objects define details about the precise location and vulnerabilities of an exposure, making DLM risk analysis possible.

  • The address object defines the specific address of a location. The DLM uses specific information about the location to better assess the vulnerability of the location. To learn more, see the [Address] schema docs.
  • The property object provides detailed information about a property, which enables the DLM to assess the vulnerability of the location to catastrophe events. To learn more, see the [Property] schema docs.

The location object enables you to provide detailed information about building attributes, coverages, reinsurance cessions, and peril attributes related to business interruption (biDetail), earthquake peril (eqDetail) , windstorm peril (wsDetail) , convective storm/winterstorm, flood (flDetail), and fire (frDetail).

Add location coverage

The POST /locations/{id}/coverage service enables you to define the terms of risk or liability for losses such as buildings, personal property, and business interruptions at a specific location.

Two required parameters, the id of the location and the datasource, are specified in the endpoint of the request.

curl --location --request POST 'https://{host}/riskmodeler/v1/locations/4/coverage/?datasource=postman_edm' \
--header 'Content-Type: application/json' \
--header 'Authorization: {api_key}' \
--header 'Content-Type: application/json' \
--data-raw '{
    "waitingPeriod": 0,
    "id": 0,
    "label": {
        "id": 0,
        "code": "",
        "name": ""
    },
    "eqslModifier": 0,
    "lossType": "Building",
    "percentSprinkler": 0,
    "value": 0,
    "biPoi": 0,
    "deductible": 0,
    "coverageModifier": {
        "id": 0,
        "code": "",
        "name": ""
    },
    "accumulation": "Building",
    "limit": 0,
    "peril": {
        "id": 0,
        "code": "",
        "name": ""
    },
    "isValid": false
}'

All other parameters are specified in the request body. The location coverage object may be used to define the terms of location-level coverage for a specific location including maximum insurer liability, the perils covered, and coverage modifiers. All locationCoverage object properties are optional.

  • The waitingPeriod specifies a waiting period deductible in days that applies to to business interruption coverage.
  • The id field defines the ID number of the covered location.
  • The label field specifies an ExposureValue object that identifies peril detail.
  • The eqsModifier field specifies the grade of contents covered by in case of an earthquake sprinkler leakage (EQSL) peril.
  • The lossType field identifies the loss type covered. One of Building, Contents, BI, or CombinedCvg.
  • The percentSprinkler identifies the percentage of building contents that are beneath a sprinkler and susceptible to water damage.
  • The value field identifies the full replacement value of covered buildings and contents and the value of one year of income for business interruption coverage.
  • The biPoi field identifies the business interruption period of indemnity in months.
  • The deductible field specifies the location coverage deductible.
  • The peril field identifies the perils covered.
  • The isValid field is a boolean value that indicates whether coverage for a location is valid (1) or invalid (0).

For detailed information on location coverage terms, see the RiskLink® and RiskBrowser® 18 Database Schema.


Did this page help you?