New updates and improvements to Herald's API.
If you’ve been keeping up with our changelog, you know that we release multiple new insurance products every month- but the work doesn’t stop there. Every product has its own set of class codes with unique conditionality, which requires tedious class code mappings from our integrations team.
In this release, we added over 14,000 new supported class codes for our cyber products. This expansion included professions throughout industries like manufacturing, contracting, and agriculture, just to name a few. This is a large step forward on our mission to support every class code for our integrations.
Applications at Herald are constructed with a series of risk and coverage parameters, equivalent to underwriting and rating questions. Some parameters can have multiple values, for cases like an applicant that has multiple locations. Herald uses the property [.h-code]creates_array: true[.h-code] to communicate this.
Previously, it was hard to distinguish between unique instances of a parameter that had multiple values. In this release, we made an update to include an [.h-code]instance[.h-code] property to give each parameter a unique identifier.
Every risk and coverage parameter that has [.h-code]creates_array: true[.h-code] now includes [.h-code]instance[.h-code], with a value to define the instance in the application. For example, the first instance of location would be [.h-code]instance: location_1[.h-code], the second would be [.h-code]location_2[.h-code], and so on.
Fixes and improvements
We also made the following fixes and improvements this release:
- We introduced logic to remove additional values to multiple choice questions when [.h-code]None of the above[.h-code] is selected.
- We added more information to the phone and email schemas in dynamic application response.
- We added new optional coverage parameters to our cyber integrations.