Developers can send in an array of products to our dynamic application endpoint (/applications) and receive a list of questions required to get quotes. Over the last two weeks we updated this endpoint to make it easier to use in three main ways:
- We now set the “value” property of unanswered questions to “null” instead of omitting that property entirely. This helps developers identify unanswered questions both visually (e.g., in Postman) and programmatically.
- Certain questions ask you to submit an array of equivalent values. For example, imagine a question that asks for a list of one or more addresses defining all locations relevant to a business. Previously, we returned two unanswered instances of the location value: one marked required and one marked optional. This behavior confused developers who did not understand why the second optional location was included. Now, we start with one required location, and only return an optional location once the first location is given an address.
- Finally, we updated the order in which properties are returned from the /applications endpoint to ensure consistency. This consistency makes it easier for developers to read and understand /applications responses.