Changes in Version 1.1

Use Answer Value instead of Answer Text
We should have Value instead of Text in the request object. It means that user will send us selected value from drop-down and set Value property in the request object. Similarly like HTML list (e.g. drop-down list) works with Value and Text.

  1. Property 'text' was renamed to 'value' for answers in request object.

Example - old request without possible answers


Example - new request without possible answers


Example - old request with possible answers


Example – new request with possible answers

  1. Data type was changed from 'integer' to 'string' for property 'value' in possible answers. For rulebase, 'text' equals 'value'.

Example - old response with possible answers (Note: possible answers and other unnecessary properties are ignored in the request object so from request perspectite possibleAnswers structure change is not important)


Example - new response with possible answers

Use Relevant Nodes collection instead of single Relevant Node
Previously relevancy was defined only between additional question and one parent question. But in Hiscox rulebase additional question depends on two parent questions. Therefore we changed:

  • removed relevantNode item from node.NodeParameters property,
  • added relevantNodes array to node.NodeParameters property.

It means that structure of response is unchanged but its content was changed. The content is very important for UX functionality - in this case it affects functionality of dynamic display of additional questions.


Example - old response


Example - Example - new response: Option 1


Example - Example - new response: Option 2

API endpoint changes
We updated API endpoints at Ursula API. We would like to make similar changes on DIP API too:

  • Don’t use underscore in the underwriting endpoints – no other endpoints use it,
  • Use camel case for action names – lower case call will also work. It’s good to use camel case because it’s better readable in swagger/documentation.