Herald Changelog

HeRB Makeover

While the core functionality remains unchanged, we’ve made it easier to navigate through HeRB (Herald Request Builder) with the following enhancements:

• Collapsable request and response fields: The request and response fields in the code blocks are now collapsable, simplifying navigation to different code fields.
• Request field tabs: We’ve reorganized request fields into tabs, enabling seamless update to parameters related to Risk, Coverage and Admin Values.

Carrier Product Enhancements

We continue to build out and improve Bind:

• Expanded Bind support: Bind is now available for 1 additional MPL (Miscellaneous Professional Liability) product, bringing the total to 7 products!
• Post-Bind actions: Actions are now supported when binding certain Cyber Admitted and Surplus products.
• Error mapping improvement: We’ve updated the handling of invalid license numbers to correctly return a [.h-code]rejected[.h-code] status.

We've enhanced several carrier products to return additional data elements:

• Quote response fields: Fields including [.h-code]quote_number[.h-code] & [.h-code]prices/details[.h-code] were extended to 7 products.
• ML (Management Liability) product update: One ML product updated to support EPLI (Employment Practices Liability Insurance).

Improvements in Validation

Our ongoing focus on data quality includes improvements in data validation logic for over 100 risk and coverage parameters that will help you create a pleasant user experience:

• Optional values for [.h-code]input_types[.h-code] [.h-code]address[.h-code] and [.h-code]claim_event[.h-code] now accept an empty string as a response, which maps to a [.h-code]null[.h-code] value. Check out our other data cleaning rules.
• We extended minimum and maximum length guidance for all parameters with [.h-code]input_type[.h-code] [.h-code]integer[.h-code], [.h-code]currency[.h-code], [.h-code]long_text[.h-code], [.h-code]claim_event[.h-code] and [.h-code]address[.h-code].

Our product team grows… again!

We're excited to announce the addition of another new product manager with a background in insurtech to our growing team. We're expanding both our team and product backlog!

‍

Bind Documentation and Guides

If you’ve been keeping up with our last few changelogs, you know that we’ve released a number of features related to binding policies. This week, we released our bind documentation. This documentation walks through the entire process of getting policies via Herald, with step-by-step guides for integrating with each endpoint.

Our bind documentation walks through:

• Filling out Bind Applications: Binding a quote can require additional information unrelated to the applicants eligibility, such as payment information, agreeing to a set of terms and conditions, or uploading a signed application. Bind Applications collect this information required to bind a quote after the institution has already determined that they are willing to insure the business.
• Submitting Bind Orders: Once you’ve completed a bind application, you can submit a bind order to request a policy. When you submit a bind order, the bind application is sent to the institution to review.
• Getting Policies: Once a bind order is [.h-code]accepted[.h-code], you can get the details of the policy that was created! Every policy includes a number of policy related files provided by the institution, as well as the policy number, coverage values, and additional metadata about the policy.
• Completing Policy Actions: After providing a policy, an institution may require you to pay for the policy, upload a file, or answer additional questions. All of these requests are communicated as actions on a policy, which can be completed using the Actions endpoint.

As noted in our previous changelog, Herald currently supports bind for Cyber Insurance and Miscellaneous Professional Liability products. Check back in for new lines of business to support bind in the near future!

Fixes and Improvements

• We expanded the set of [.h-code]coverage_values[.h-code] we return for cyber policies.
• We expanded our Management Liability appetite by introducing additional underwriting questions for applicants viewed as large-risk. These questions allow applicants with larger total assets and higher employee counts to get quotes.
• We added a new input type of [.h-code]agree_to[.h-code] for questions that expect an applicant to agree to a set of terms and conditions.

We have launched bind for our first professional liability product

Our bind feature allows you to bind in addition to quote using Herald. We have added bind for our first professional liability product. Add that to the list of 5 Cyber Products you can already bind, making 6 total. The number is growing every day.

We set the stage to support bind for many more carriers

We launched 2 new features that will make bind easier to use with more products.

• What’s in it for you: Now when you bind a policy with Herald there will be more ways to get the carrier what they need instantly. And if the carrier will bind and let you get to things later, we’ll bind the policy and let you know what to do next.
• File Uploads: Many carriers require a file upload to bind a policy, such as a signed application. We launched our POST /files to allow uploading files to Herald.
• Post-Bind Actions: Some carriers require additional information after a policy is bound. We released actions as a way for you to submit required information after a policy is bound.

Look out for bind to be available for more products are we prepare to support bind at scale.

Our product team is growing!

We recently hired a new product manager with amazing industry experience (think Plaid). We are bringing the best talent so that we can make the best products for you.

‍