Introduction

HazardHub is a third-generation provider of property-level hazard risk databases. Their team translates voluminous geospatial digital data into easy-to-understand answers, providing risk assessments that can be used to make real-world decisions.

HazardHub data is obtained during the quoting process and can be used to calculate the rate. It can be shown to agents, underwriters or both.

Prerequisites

1. Obtain the API key, base URL, and endpoint from Hazard Hub: api.hazardhub.com
2. Review the data dictionary of all available data points: Hazard Hub Data Dictionary
3. Determine which data points (if any) you want configured as supplemental questions.
4. Determine which data points (if any) you want configured as rating categories.
5. Determine if you want any underwriting rules related to the new supplemental questions/rating categories.

Configuration Steps

To configure the HazardHub integration, navigate to Settings > Vendors and check the box next to HazardHub. Click the pencil icon to configure the setup. The HazardHub connection requires certain details to establish the connection. Within the dialog pop-up box enter the following details:

1. Input the API key, the base URL and details on the endpoint to connect to, as provided by the vendor. Usually, the base URL is https://api.hazardhub.com/v1 and the endpoint is risks_and_enhanced_property2 or risks_and_enhanced_property2_and_replacement_cost_data.
2. Configure the four settings as desired:
   1. 1. Enable API caching. If enabled, BriteCore will verify that HazardHub data was not acquired within the last 14 days before calling the vendor to save on extraneous vendor costs. If the property address changes in any way, BriteCore will assume that the property is different and will not use the cached data.
      2. Trigger on rate and save. If enabled, HazardHub data will be acquired when an agent clicks Rate and Save. It is recommended that caching be enabled if this option is set to minimize costs of multiple data pulls when agents test different coverage scenarios.
      3. Disable property interface. If enabled, hides the HazardHub Data from the Risk (Property) tab for all users (agents and underwriters).
      4. Disable property interface only for agents. If enabled, hides the HazardHub Data section from the Risk (Property) tab for agents.
3. Configure the Mapping Settings by clicking the Mapping Settings link. This section contains the Rating Mappings and Supplemental Mappings tables. Rating Mappings is where you should map data to rating categories (map from each HazardHub Mapping/HazardHub Value pair to BriteCore Mapping/BriteCore Value pair) and Supplemental Mappings is where you should map data points to supplemental questions (map from each HazardHub Mapping item to BriteCore Label). Mappings are required only if the data should be passed to categories or supplemental questions. If using the HazardHub data in rating evaluations only, use of the mappings is not required.
   1. 1. Rating Mappings. The Rating Mappings table is configured as follows:
         1. 1. HazardHub Mapping. Maps from the JSON path of the returned result from the HazardHub API. Note: it is very likely that this path will be repeated for multiple values as demonstrated in the example below.
            2. HazardHub Value. Possible values for each of the JSON items. This field can also contain certain keywords to trigger format translation in the mapping process. Refer to the Translators section, below.
            3. BriteCore Mapping. Maps to the BriteCore category of the HazardHub line item. As with the HazardHub Mapping, it is very likely that the category will be repeated for multiple values.
            4. BriteCore Value. The category values that each HazardHub value should map to in BriteCore. Use an asterisk (‘*’) when a Translator is used in the HazardHub Value.
      2. Supplemental Mappings.
         1. 1. HazardHub Mapping. Maps from the JSON path of the returned result from the HazardHub API.
            2. BriteCore Label. Maps the HazardHub Mapping data to the BriteCore supplemental questions. The value entered in the BriteCore Mapping will be the supplemental question name.
4. Click Save to close the mapping settings, then Done to save the HazardHub configuration pop-up screen.

Translators

BriteCore supports format translators for the values provided by HazardHub. Translator keywords are case sensitive.

• ‘capitalize’ - Capitalizes the first letter of the string
• ‘upper’ - Makes returned value uppercase
• ‘lower’ - Makes returned value lowercase
• ‘ucfirst’ - Capitalizes the first letter of each word
• ‘string’ - Converts response to a string value
• ‘integer’ Used for integer response
• ‘numeric’ - Used for decimal responses
• ‘anything’ - Performs no transformation

Note: ’integer’ and ‘numeric’ translators do not enforce a value type. If used on a string, the output will remain a string. Instead, these translators are useful to create simple pass-throughs for numeric values such as year numbers.

Here is an example of a mapping assuming the risks_and_enhanced_property2 endpoint:

Here is a brief example of Supplemental Mappings assuming the risks_and_enhanced_property2 endpoint: