Herald Changelog

Bind in HeRB

The bind feature is now available in Herald’s developer portal, allowing users to create a bind order from an active quote and retrieve policies.

Additionally, you are also now able to complete actions in the portal, which enables you to submit additional information to institutions after the policy has been created. It’s not uncommon for an institution to request additional information after providing a quote or policy, and actions allow you to submit this information.

HeRB supports two types of actions to interact with an existing policy: visiting a link provided by the institution or submitting an application (similar to how you submit a quote application). Read the step-by-step guide for completing actions here.

Parameters API Quote Relevance

As noted in our last changelog, we’ve recently introduced the GET/insurance_parameters endpoint to provide users with access Herald’s parameter information in a standardized, intuitive, and machine-ingestable format.

In the most recent release, we’ve added quote relevance (conditionality)  information of parameter to the response body, which enable developers to dynamically handle complex carrier underwriting rules. Please read more about how Herald approaches and standardizes conditionality here.

New quote processor rollout completed

As detailed in the recent high impact changes update, the new quote processor rollout to production is complete as of August 30, which will deliver faster quotes and an improved developer experience by processing files separately from quotes.

Feature enhancements and bug fixes

• We added additional tooltips to clarify carrier question definitions (e.g., long-term liabilities)
• We added agree-to parameters to a certain carrier’s application to separate text-heavy attestation statements from the rest of the application and enhance user experience
• We fixed a bug in our developer portal related to sharing application links

‍

‍

‍

Parameters API beta release

Parameters are the building blocks Herald customers use to create applications for commercial insurance quoting and binding.

As a step towards providing our users with more visibility into Herald question sets and eventually enabling question set management, we recently launched the GET/insurance_parameters endpoint, which allows users to access Herald’s parameter information in a standardized, intuitive, and machine-ingestable format.

You can now send request to GET/insurance_parameters, and Herald will return a list of parameters and their metadata that the user has access to.

Note that /insurance_parameters is a beta endpoint and subject to change. If you would like to request access to this beta release, please email support@heraldapi.com.

Producer management & disablement

• You can now disable producers and continue to manage entities related to the disabled producer.  The /producers API response now contains an “enabled” boolean which provides information on a producer’s status., which defaults to true if not provided. You can update producer status by sending a PUT or PATCH request (see below) via the producer’s endpoint to modify this value.
• In conjunction, we’ve introduced the PATCH/producers endpoint, which allows users to update any producer fields editable via PUT and reduce accidental changes when disabling producers.

Bind in Herald Developer Portal (HeRB)

• You can now use HeRB to bind policies and simulate the underlying API workflow for binding an application, creating and viewing bind orders, and retrieving details for the policy.

Developer Portal 2.0 is live

• As previewed in our last changelog, developer portal 2.0 is now live.

More features & enhancements

• We’ve updated our integration with one of our carriers to support a parameter pertaining to occupancy types to be captured at the location level instead of policy level
• We’ve made updates to a MPL product to reflect carrier’s filing changes by state
• We’ve made enhancements to a ML product to stay in sync with carrier application requirements
• We’ve made updates to time-based parameters for ML products to allow for more flexible enum inputs
• We’ve added the ability to request bind order for a carrier’s ML product
• We’ve fixed a bug related to the foreign location parameter for an ML product

‍

Developer Portal 2.0

In March, we released our Developer Portal with full user management, which allows customers to add members of their company to integrate with Herald and monitor activity across all environments.

Next up, we are bringing you Developer Portal 2.0 (release to be announced soon via banner in Developer Portal 1.0), with more seamless customer experience and new features, including:

• Stateful stepper: enable users to refresh, update, and hit return on forms without losing progress
• Lag-free forms
• Dev mode toggle
  • Developer mode toggle allows tailored front-end displays for different user types
  • In non-dev-mode, users can view the application by section navigation or missing fields
• Other features
  • Documentation now shown as a pop-up when users hit “Documentation” button on top right
  • Default producer selection

New Management Liability Product

Herald launched 1 new integration for our Management Liability line of business, bringing our total supported Management Liability Products to 6.

Feature Enhancements & Bug Fixes

• We updated async quote response to show the latest quote summary file from carrier instead of all historical versions. Prior files will still be available via /files endpoint for retrieval
• We removed duplicated risk parameters for a BOP product
• We fixed a bug related to chained conditional logic to ensure that updates to upstream conditional parameters are properly reflected in all downstream logic

‍