Our API is stateless, and each request/response is unique. The Advice represented in the response, however, does have a "state", which is communicated in the form of Variable outputs. For example, if an API request includes Income = 150000 and Income_Spouse = 150000, the API could return a Variable named Income_Total with a computed value of 300000.

Last year, we added a new API response format detailed in New API response format. This week, we've changed the API slightly: the _links property is now simply links.

We are continuously improving not only the quality and breadth of our Advice but also the appearance of it. Our Advice Builder supports writing Advice in Markdown syntax, and our API can return parsed HTML when using the HTML Advice Content Type.

We are excited to announce a brand-new format for our Assumptions. Our Assumptions (available in assumptions[]) is a list of text-based assumptions shown in the screenshot below. These Assumptions are crucial to personalizing a given scenario. Typically represented as a bulleted list like this:

Today, we are introducing a new "Follow on" Advice feature. This capability allows our Analysts to write Advice text more clearly and concisely in Advice Builder.

A Backlink links a Variable in the Advice text to the question where the user can modify the input. Usually, an Input Request is associated with a single Variable. For example, the question "How old are you?" is associated with the Age_Now Variable.

When presenting users with multiple-choice questions, we have long supported the idea of an "other" answer.

The Taffrail Advice Builder supports Markdown syntax for writing and formatting Advice text. If you know Markdown, you know Markdown tables are... fun.

There are a series of data-backlink-* properties on <taffrail-var> web components generated by the Taffrail API when using the HTML Advice Content Type.

Every Backlink used in Advice has a series of attributes on the web components generated by the Taffrail API when using the HTML Advice Content Type.