GuidesAPI ReferenceDiscussions
HomeGuidesAPI ReferenceChangelogDiscussions
GuidesAPI ReferenceDiscussions

## Event Summary

Certain processes in Blend are referred to as "follow ups" which broadly denotes a task that requires various conditions to be met for its completion. This may manifest as, for example, a request for tax documents or confirmation of a form of proof of identity that require a party to an application in Blend to login and perform some action (e.g. answer a question, upload a document, sign a document, etc.).

These "follow ups" have state, and the events that surround them are designed to help integrators trigger backend processing logic related to those requests (e.g. after a "follow up" is completed, download the associated document or file from the party).

## Updated

## Firing Condition

When the state of a follow up changes, this event is fired after the state change and associated data updates have been committed to the Blend data model, thereby ensuring that API requests against the follow up after the event is emitted are linearizable by timestamp.

## Fields

The fields object will contain, at minimum:

  1. "solutionSubType" - the type of application the party is associated with (e.g., HELOC, MORTGAGE, etc.)

  2. "applicationId" - the UUID of the application the party is associated with.

  3. "status" - a string value the denotes the state of the follow up.

## Example