Applicant- and Agent-Facing Text
New updates and improvements to Herald's API.
Tailoring question text to your audience
An applicant, or an agent representative, must answer questions about their level of risk and the coverage items they seek in order to get an insurance quote. This week we launched support for alternative versions of the same question text: one oriented towards the applicant and one oriented towards their agent. We now provide applicant- and agent-facing text for every risk and coverage parameter in Herald.
With this feature, our customers can customize which type of question text their user sees based on the experience they're trying to build. Prior to this release Herald only offered one version of the text for each question that was provided by the relevant carriers. This text was inconsistent across the multiple carriers integrated with Herald. Sometimes this text was written for the applicant, other times for the agent.
These text options appear in the [.h-endpoint-link]/applications[.h-endpoint-link] responses, located within the [.h-code]parameter_text[.h-code] object for each risk and coverage parameter. We have also documented the details around applicant- and agent-facing text in the Appendix for every parameter in Herald.
Fixes and Improvements
- We fixed a bug that was returning quotes without a [.h-code]portal_link[.h-code] for certain Cyber products.
- We enhanced Cyber products to accept more values for Aggregate Limits.
- We improved the error messaging around certain malformed requests to our /quotes endpoint.
- We fixed a bug that was throwing an erroneous [.h-code]400[.h-code] error when Content-Type was not set to “application/json.”