pub struct FollowUpSchema {
pub id: String,
pub application_id: String,
pub type_: String,
pub status: String,
pub comments: Option<String>,
pub client_follow_up_reference_id: Option<String>,
pub due_date: Option<String>,
pub requested_at: String,
pub requested_by: String,
pub context: Value,
}
Fields§
§id: String
§application_id: String
§type_: String
Types of follow-ups that can be returned. This is a superset of FollowUpType that includes the ‘SYSTEM’ follow-up type corresponding to follow-ups that were requested by Blend automatically, and the ‘DOCUMENT_WET_SIGNATURE’ follow-up type which is the type of wet-sign follow-ups issued when an external e-sign (‘DOCUMENT_SIGNATURE’ type) follow-up request fails.
status: String
Follow-up statuses REQUESTED - Follow-up has been requested and is awaiting completion by the borrower IN_PROGRESS - Follow-up has been started by at least one borrower COMPLETED - Follow-up has been completed by the borrower and if a document request, reviewed and accepted by the lender in the Blend lender UI. COMPLETED_EXTERNALLY - Follow-up has been marked as completed externally in the Blend lender UI PENDING_REVIEW - Follow-up has been completed by the borrower and can be reviewed and accepted or rejected by the lender in the Blend lender UI REJECTED - Follow-up has been completed by the borrower and was reviewed and rejected by the lender in the Blend lender UI
comments: Option<String>
Comments displayed to the party on the follow-up
client_follow_up_reference_id: Option<String>
Unique id passed by client for referencing follow-up
due_date: Option<String>
UTC Timestamp of follow-up due date
requested_at: String
UTC Timestamp of when the follow-up was requested
requested_by: String
The ID of the user that requested the follow-up, or ‘SYSTEM’ for automatically requested follow-ups
context: Value