Herald changelog

By The Herald team

Herald changelog - Full Transparency





Subscribe to our newsletter

By subscribing, you agree with Revue’s Terms of Service and Privacy Policy and understand that Herald changelog will receive your email address.

Herald changelog - Full Transparency
By The Herald team • Issue #33 • View online
Herald builds digital infrastructure for commercial insurance. Originally published here.

Our API Reference is Open to the Public
This week we officially made our API Reference public, which contains details about Herald’s full API schema. Previously, we limited access to our API Reference to customers only, using a login. Our API reference contains sample requests, sample responses, and the ability to make mock calls.
We previously released our public-facing Herald Docs, which document the core concepts and principals of Herald. With the addition of our now-public-facing API Reference, you have full transparency into our product. Our API Reference provides visibility to both our master and beta branches, documenting both released and unreleased features.
Fixes and Improvements
  • We improved our data cleaning to strip everything after a trailing / from domain names. Previously submitting a domain name such as heraldapi.com/docs would cause an error, but our data cleaning now transforms it to heraldapi.com
  • We fixed a bug that allowed users to submit a string of characters, such as yes, as a valid domain name.
  • We updated domain name to be an optional parameter for certain products.
  • We fixed a bug that required a risk parameter for 5-year claim history when using certain cyber products, even when it was irrelevant.
Did you enjoy this issue?
The Herald team

Herald changelog and updates

In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue