1 | Data Dictionary | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
2 | For Reporting Dashboard and Reporting API | |||||||||
3 | HOW TO USE: This document provides information on fields and descriptions for data available in the Reporting Dashboard and Reporting API. ► Search for a specific field or topic of interest (cmd + F on a Mac, or Ctrl + F on Windows), or browse all fields available in each of the reports. ► Navigate to the User Guide and Document Changelog using the tabs in the top left corner of the page. You can find links to additional resources in the User Guide tab. | |||||||||
4 | ||||||||||
5 | ||||||||||
6 | ||||||||||
7 | ||||||||||
8 | Application List / Loans | |||||||||
9 | Reporting Dashboard Report: Application List | |||||||||
10 | Reporting API Endpoint: Basic Loan Data - https://api.blendlabs.com/reporting/loans | |||||||||
11 | This report is one row per loan with attributes and milestones for that loan. Use it to find things like conversion rate, which apps have not been submitted yet, or where your loan came from. | |||||||||
12 | ||||||||||
13 | FIELD | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
14 | Loan ID | loanID | PRIMARY KEY - The UUID of the application in Blend's system. The static identifier that should be used to connect the application's identity across Blend and external integrations | STRING | v2.0.0 | 11/1/2019 | ||||
15 | LOS Primary Key | losPrimaryKey | The primary key of the loan in the LOS | STRING | v2.0.0 | 11/1/2019 | ||||
16 | CRM Primary Key | crmPrimaryKey | The CRM primary key of the loan in the LOS | STRING | v4.0.0 | 11/1/2019 | ||||
17 | Loan Reference Number | loanNumber | The unique reference number associated with the loan | STRING | v2.0.0 | 11/1/2019 | ||||
18 | Creator User ID | creatorUserId | The user ID for the user that originated the loan | STRING | v4.0.0 | 12/17/2020 | ||||
19 | Primary Lender User ID | primaryAssigneeUserId | The unique user ID associated with the primary assignee | STRING | v4.0.0 | 11/1/2019 | ||||
20 | Primary Lender Name | primaryAssigneeName | The full name of the primary assignee | STRING | v4.0.0 | 12/17/2020 | ||||
21 | Primary Lender User Email | primaryAssigneeEmail | The email address of the primary assignee | STRING | v4.0.0 | 12/17/2020 | ||||
22 | All Current Assignees | allCurrentAssignees | A JSON array containing the user ID, name, and email of all current assignees on the loan | STRING | v4.0.0 | 12/17/2020 | ||||
23 | Loan Type | loanType | The specific product (Mortgage, HELOAN, HELOC, Auto, etc) | STRING | v2.0.0 | 11/1/2019 | ||||
24 | Loan Purpose Type | loanPurposeType | REFINANCE' or 'PURCHASE' for Mortgage loans. Will be set to 'OTHER' or null for other loan types. | STRING | v2.2.0 | 11/1/2019 | ||||
25 | Application Source | appSource | The source of the application (e.g. CRM, LOS) | STRING | v2.0.0 | 11/1/2019 | ||||
26 | Application Source Name | appSourceName | The name of the LOS or CRM that the application was imported from. Optional field to use when creating loans via API | STRING | v2.0.0 | 11/1/2019 | ||||
27 | Application Lead Source | appLeadSource | Specifies how an app was created: BORROWER: Borrower created the loan (e.g. borrower self served via link on website) LENDER: Lender created the loan PUBLIC_API: Loans pushed into Blend using the Public API INGEST: Generally due to a direct integration with a CRM | STRING | v2.2.0 | 11/1/2019 | ||||
28 | Loan Application Program | appProgram | The loan program of the application, possible values include: STATE_AGENCY, VA, FHA, CONVENTIONAL, LOCAL_AGENCY, USARURAL_DEVELOPMENT, PUBLIC_AND_INDIAN_HOUSING, OTHER | STRING | v4.0.0 | 12/17/2020 | ||||
29 | Loan Application Marketing Tag | appMarketingTag | The unique marketing identifier on the loan to help users track their top of funnel campaigns | STRING | v2.2.0 | |||||
30 | Asset State | assetState | The registered address state on the asset | STRING | v4.0.0 | 12/17/2020 | ||||
31 | Asset Purchase Price | assetPurchasePrice | The purchase price of the asset | STRING | v4.0.0 | 12/17/2020 | ||||
32 | Loan Application Status | loanApplicationStatus | The current status of the loan application (DENIED, IN_PROGRESS, SUBMITTED) | STRING | v4.0.0 | 12/17/2020 | ||||
33 | LOS Milestone | losMilestone | An optional enumerated field sent by lenders who have shared this data via the home-lending/applications/los-milestones endpoint in our public API. Options are [SUBMITTED. UNDERWRITING, CONDITIONAL_APPROVAL, APPROVED, CLOSING, CLOSED] | STRING | v4.3.0 | 12/17/2020 | ||||
34 | LOS Milestone Last Updated Datetime | losMilestoneLastUpdatedDatetime | This field is a corresponding timestamp for when the los_milestone field was last updated by a lender via the home-lending/applications/los-milestones endpoint in our public API | TIMESTAMP_TZ | v4.3.0 | 12/17/2020 | ||||
35 | Credit Pulled Date | FirstCreditPullDatetime | The timestamp when credit was first pulled on the loan (soft or hard credit). See PAB activities table for more details on type of pull | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
36 | Borrower SSN Flag | primaryBorrowerSsnFlag | A flag denoting if the primary borrower has provided their SSN | BOOLEAN | v4.0.0 | 12/17/2020 | ||||
37 | Borrower Credit Consent Date | primaryBorrowerCreditConsentDate | The timestamp that the primary borrower provided credit pull consent | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
38 | Borrower E-Consent Flag | primaryBorrowerEconsentFlag | A flag denoting that the primary borrower has activated their account and checked the box for eConsent false - borrower has declined. This is achieved by the lender selecting decline in the borrower section; typically, the borrower will be contacted by or contact the LO to get this information Null - borrower has not reached this part of the app yet (or has not created an account) | BOOLEAN | v4.0.0 | 12/17/2020 | ||||
39 | Coborrower SSN Flag | coborrowerSsnFlag | A flag denoting if the coborrower has provided their SSN | BOOLEAN | v4.0.0 | 12/17/2020 | ||||
40 | Coborrower Credit Consent Date | coborrowerCreditConsentDate | The timestamp that the coborrower provided credit consent | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
41 | Coborrower E-Consent Flag | coborrowerEconsentFlag | A flag denoting that the coborrower has activated their account and checked the box for eConsent false - borrower has declined. This is achieved by the lender selecting decline in the borrower section; typically, the borrower will be contacted by or contact the LO to get this information Null - borrower has not reached this part of the app yet (or has not created an account) | BOOLEAN | v4.0.0 | 12/17/2020 | ||||
42 | Loan Application Follow Up Only Flag | followUpOnlyFlag | A flag that indicates that the application was a follow-up only loan, the lender used Blend to issue follow ups to the borrower | BOOLEAN | v4.0.0 | 12/17/2020 | ||||
43 | Borrower Connectivity Flag | connectivityFlag | A flag that indicates whether or not an asset statement (GAS) was generated from source data in a borrower’s bank account and is eligible for GSE rep and warrant programs (D1C/AIM). This field does not include successful asset connectivity in cases that Blend is unable to access high enough quality source data for the GSE programs, but will pull a PDF instead and the borrower will not be prompted to upload bank statements (Assets Statement Fallback). | BOOLEAN | v4.0.0 | 12/17/2020 | ||||
44 | Borrower Blend Income Verification Flag | blendIncomeSuccessFlag | A flag that indicates whether the loan had at least one Blend Income Report generated (a borrower's income was successfully verified) | BOOLEAN | v5.1.0 | |||||
45 | Borrower TWN Success Flag | twnSuccessFlag | A flag that indicates that a successful match was found on the borrower using The Work Number | BOOLEAN | v4.0.0 | 12/17/2020 | ||||
46 | Loan Application Realtor Flag | hasRealtorFlag | A flag that indicates the borrower selected they are working with a realtor on their application | BOOLEAN | v4.0.0 | 12/17/2020 | ||||
47 | Unassigned Loan Flag | unassignedOnSubmitFlag | For Mortgage/Heloc/Heloan only - A flag that indicates the loan was unassigned upon submit. This field will not change if a loan is assigned. 'true' = the loan was unassigned at submission 'false' = the loan was assigned at submission null = the loan may not have been submitted yet, or is is a non-mortgage product | BOOLEAN | v4.0.0 | 12/17/2020 | ||||
48 | Sign-up URL | signupUrl | For Mortgage/Heloc/Heloan only - The sign-up URL the borrower used to apply. Can be used with the unassignedOnsubmitFlag field to diagnose faulty referral links | STRING | v4.0.0 | 12/17/2020 | ||||
49 | Preapproval Letter Generated Date | preapprovalLetterDatetime | The timestamp a preapproval letter was generated on the loan | TIMESTAMP_TZ | v4.0.0 | |||||
50 | Loan Application Creation Date | createdDatetime | The timestamp when the loan was created | TIMESTAMP_TZ | v2.0.0 | 11/1/2019 | ||||
51 | Loan Application Start Date | borrowerStartedDatetime | The timestamp when the borrower started the application | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
52 | Loan Application Submitted Date | borrowerSubmittedDatetime | The timestamp when borrower submitted the application | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
53 | Lender Take Over Datetime | takeOverDatetime | The timestamp when the loan application was first taken over by the lender user | TIMESTAMP_TZ | v3.1.0 | 12/17/2020 | ||||
54 | Loan Application Exported Date | estExportedDatetime | The timestamp when the application was exported. Field is appended with estimated, as this field is not meant to be used for compliance and reconciliation purposes | TIMESTAMP_TZ | v3.1.0 | 12/17/2020 | ||||
55 | Last Updated Date | estLastUpdatedDatetime | The timestamp the loan was last updated by the system. Can be used to filter on to find loans that have been updated. Field is appended with estimated, as this field is not meant to be used for compliance and reconciliation purposes and specific actions may not be considered as a "last updated" | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
56 | Last Touched Date | estLastTouchedDatetime | The timestamp the loan was last touched (by a borrower or lender user). Field is appended with estimated, as this field is not meant to be used for compliance and reconciliation purposes and specific actions may not be considered as a "last touched". | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
57 | Last Touched By User ID | lastTouchedByUserId | The ID of the user to last touch the loan (can be borrower or lender user) | STRING | v4.0.0 | 12/17/2020 | ||||
58 | Loan Application Archived Date | estArchivedDatetime | The timestamp when the application was archived. Field is appended with estimated, as this field is not meant to be used for compliance and reconciliation purposes | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
59 | Loan Application Deleted Date | estDeletedDatetime | The timestamp when the application was deleted. Field is appended with estimated, as this field is not meant to be used for compliance and reconciliation purposes | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
60 | Loan Application Purged Date | estPurgedDatetime | The timestamp when the application was purged. Field is appended with estimated, as this field is not meant to be used for compliance and reconciliation purposes ("estimated" in this case does not predict when a loan will be purged. This field is only for loans that have already been purged) | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
61 | Days Since Last Touch | daysSinceLastTouch | Number of days since the loan was last touched (from when the report was generated) | NUMBER | v2.2.0 | 11/1/2019 | ||||
62 | Application Start To Submit Time | appStartToSubmitMinutes | Number of minutes from when the app was started to when the primary borrower has completed the review and submit process | NUMBER | v4.0.0 | 12/17/2020 | ||||
63 | As Of Date | asOfDate | The timestamp for when the report was generated | TIMESTAMP_TZ | v2.0.0 | 11/1/2019 | ||||
64 | ||||||||||
65 | ||||||||||
66 | ||||||||||
67 | ||||||||||
68 | ||||||||||
69 | PAB Activities | |||||||||
70 | Reporting Dashboard Report: PAB Activities | |||||||||
71 | Reporting API Endpoint: PAB Activities - https://api.blendlabs.com/reporting/lender-pab-activities | |||||||||
72 | This report is one row per LO Toolkit action (formerly "Pre Approval Builder" (please note this report also includes LO Toolkit actions done automatically). You can use it to see which of your users are adopting different LO Toolkit features, or more specific credit pull information on a loan | |||||||||
73 | ||||||||||
74 | FIELD LONG NAME | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
75 | Activity ID | activityId | PRIMARY KEY - Unique ID of the activity | STRING | v4.0.0 | 12/17/2020 | ||||
76 | Loan ID | loanID | The UUID of the application in Blend's system. The static identifier that should be used to connect the application's identity across Blend and external integrations | STRING | v4.0.0 | 12/17/2020 | ||||
77 | Loan Reference Number | loanNumber | The unique reference number associated with the loan | STRING | v4.3.0 | 8/24/2021 | ||||
78 | Loan Type | loanType | The specific product (Mortgage, HELOAN, HELOC, Auto, etc) | STRING | v4.0.0 | 12/17/2020 | ||||
79 | Loan Purpose Type | loanPurposeType | REFINANCE' or 'PURCHASE' for Mortgage loans. Will be set to 'OTHER' or null for other loan types. | STRING | v4.0.0 | 12/17/2020 | ||||
80 | Application Lead Source | appLeadSource | Specifies how an app was created (BORROWER, LENDER, INGEST, PUBLIC_API) | STRING | v4.0.0 | 12/17/2020 | ||||
81 | User ID | userId | User ID for the user that completed the action (can be the user ID for a borrower or lender, or 'system') | STRING | v4.0.0 | |||||
82 | User Type | userType | The type for the user that completed the action. Can be system, borrower, or lender | STRING | v4.0.0 | 12/17/2020 | ||||
83 | Lender Name | lenderUserName | If user_type is a lender, the full name of the lender user that completed the activity | STRING | v4.0.0 | 12/17/2020 | ||||
84 | Lender User Email | lenderUserEmail | If user_type is a lender, the email address of the lender user that completed the activity | STRING | v4.0.0 | 12/17/2020 | ||||
85 | Activity Type | activityType | Which PAB Activity was done on the loan. Can be one of the following: ecoa updated pulled credit selected a product sent pre-approval letter ran desktop underwriter fees pulled initiated automated underwriting sent loan cost worksheet | STRING | v4.0.0 | 12/17/2020 | ||||
86 | Activity Datetime | activityDatetime | Timestamp for when the activity was done on the loan | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
87 | Activity Success | activitySuccess | Field indicating whether the activity was successful or not | BOOLEAN | v4.0.0 | 12/17/2020 | ||||
88 | Credit Pull Type | creditPullType | For credit pull events - the type of credit pull (Hard or Soft) | STRING | v4.0.0 | 12/17/2020 | ||||
89 | Credit Bureaus | creditBureaus | For credit pull events - a JSON array containing the bureaus where credit was pulled from | STRING | v4.0.0 | 12/17/2020 | ||||
90 | Credit Bureau Type | creditBureauType | For credit pull events - the type of pull (single or tri) | STRING | v4.0.0 | 12/17/2020 | ||||
91 | Credit Joint | creditJoint | For credit pull events - if the credit was pulled jointly | BOOLEAN | v4.0.0 | 12/17/2020 | ||||
92 | Credit Action Type | creditActionType | For credit pull events - the action on the pull | STRING | v4.0.0 | 12/17/2020 | ||||
93 | AUS Product | ausProduct | For activities 'initiated automated underwriting' or 'ran desktop underwriter' - the specific AUS product used ('desktopUnderwriter', 'loanProductAdvisor') | STRING | v6.0.0 | 3/21/2023 | ||||
94 | AUS Recommendation | ausRecommendation | For activities 'initiated automated underwriting' or 'ran desktop underwriter' - what the recommendation is ('Approve/Eligible', 'Approve/Ineligible', 'Refer with Caution', etc ). Please note - this field was renamed in v6.0 of the Reporting API. For versions 4.0.0-5.3.0 (released 12/17/2020) the field is referred to as duRecommendation | STRING | v6.0.0 | 3/21/2023 | ||||
95 | ||||||||||
96 | ||||||||||
97 | ||||||||||
98 | ||||||||||
99 | ||||||||||
100 | Document Meta | |||||||||
101 | Reporting Dashboard Report: Document Meta | |||||||||
102 | Reporting API Endpoint: Document Metadata - https://api.blendlabs.com/reporting/documents | |||||||||
103 | This report is one row per document generated on a loan. | |||||||||
104 | ||||||||||
105 | FIELD LONG NAME | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
106 | Document ID | documentId | PRIMARY KEY - Unique ID of the document | STRING | v2.0.0 | 11/1/2019 | ||||
107 | Loan ID | loanID | The UUID of the application in Blend's system. The static identifier that should be used to connect the application's identity across Blend and external integrations | STRING | v2.0.0 | 11/1/2019 | ||||
108 | Uploaded By User ID | uploadedByUserId | The User ID for the user who uploaded the document | STRING | v4.0.0 | 12/17/2020 | ||||
109 | Uploaded By User Type | uploadedByUserType | The type of user that uploaded the document. Can be one of the following: system = Documents automatically uploaded by Blend (e.g. asset statements, compliance reports, etc) external_api = Documents uploaded to Blend through the public API by a third party (e.g. Disclosures, Document Signature Requests, etc.) internal_api = Additional Blend services may appear as using the internal API to upload documents (e.g. Verification of Income, Pre Approval Letters, etc) borrower = uploaded by a borrower lender = uploaded by a lender user" | STRING | v4.0.0 | 12/17/2020 | ||||
110 | Document Type | type | The type of document uploaded. Full list of document types can be found at https://info.blend.com/rs/287-UGB-469/images/BlendAPIDocTypes2.csv | STRING | v2.0.0 | 11/1/2019 | ||||
111 | Document Source | source | The source of where the document came from. Can be 'connectivity' for documents pulled through Blend's connectivity, or 'user' for all other documents | STRING | v2.0.0 | 11/1/2019 | ||||
112 | Created Datetime | createdDatetime | The UTC timestamp for when the document was uploaded | TIMESTAMP_TZ | v2.0.0 | 11/1/2019 | ||||
113 | Loan Type | loanType | The specific product (Mortgage, HELOAN, HELOC, Auto, etc) | STRING | v4.0.0 | 12/17/2020 | ||||
114 | Report Generation Time | asOfDate | The timestamp for when the report was generated | TIMESTAMP_TZ | v2.0.0 | 11/1/2019 | ||||
115 | ||||||||||
116 | ||||||||||
117 | ||||||||||
118 | ||||||||||
119 | ||||||||||
120 | Borrower Users | |||||||||
121 | Reporting Dashboard Report: Borrower Users | |||||||||
122 | Reporting API Endpoint: Borrower Users - https://api.blendlabs.com/reporting/borrowers | |||||||||
123 | This report is one row per applicant. Please note all sensitive data is scrubbed and is not available in reporting (this includes applicant email, phone number, address, etc). Use this report to see different milestones for each borrower. | |||||||||
124 | ||||||||||
125 | FIELD | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
126 | Party ID | partyId | PRIMARY KEY - Unique uuid for a party on the loan (borrower or coborrower). If the same applicant is a party on multiple applications, they will have a different Party ID for each application, but their User ID will remain constant. | STRING | v2.0.0 | 11/1/2019 | ||||
127 | User ID | userId | Unique User ID associated with the applicant, which will remain constant across applications if the same applicant opens multiple applications. | STRING | v2.0.0 | 11/1/2019 | ||||
128 | Loan ID | loanId | The UUID of the application in Blend's system. The static identifier that should be used to connect the application's identity across Blend and external integrations | STRING | v2.0.0 | 11/1/2019 | ||||
129 | Loan Reference Number | loanNumber | The unique reference number associated with the loan | STRING | v4.3.0 | 8/24/2021 | ||||
130 | Role | role | Either the borrower or coborrower | STRING | v2.0.0 | 11/1/2019 | ||||
131 | Activation Datetime | activationDatetime | The timestamp (in UTC) that the borrower accepts Terms of Service | TIMESTAMP_TZ | v2.0.0 | 11/1/2019 | ||||
132 | Invited Datetime | invitedDatetime | The timestamp (in UTC) that the lender first sends invitation to borrower | TIMESTAMP_TZ | v2.0.0 | 11/1/2019 | ||||
133 | Credit Pulled Datetime | creditPulledDatetime | The timestamp (in UTC) when credit was first pulled. See PAB Activities for more granular credit pull information | TIMESTAMP_TZ | v2.2.0 | 11/1/2019 | ||||
134 | Assets Pulled Datetime | assetsPulledDatetime | The most recent timestamp (in UTC) that the borrower successfully connected their account and generated an assets statement. Please note this only includes instances where an asset statement (GAS) was generated from source data in a borrower’s bank account that is eligible for GSE rep and warrant programs (D1C/AIM). This field does not include successful asset connectivity in cases that Blend is unable to access high enough quality source data for the GSE programs, but will pull a PDF instead and the borrower will not be prompted to upload bank statements (Assets Statement Fallback) | TIMESTAMP_TZ | v2.2.0 | 11/1/2019 | ||||
135 | Blend Income Verified Datetime | incomeVerifiedDatetime | The most recent timestamp (in UTC) that a Blend Income Report was generated for that borrower (i.e. the borrower's income was successfully verified) | TIMESTAMP_TZ | v5.1.0 | 2/22/2022 | ||||
136 | Workflow Milestone | workflowMilestone | Most recently completed Blend workflow | STRING | v2.2.0 | 11/1/2019 | ||||
137 | Login Method | loginMethod | The method the user used to login (email, SSO, borrowerSAML, anonymousBorrower, shortForm) | STRING | v3.2.0 | 11/1/2019 | ||||
138 | User Agent | userAgent | The most recent borrower user agent. Can be used to derive the last device type used | STRING | v4.1.0 | 3/1/2021 | ||||
139 | Last Updated Datetime | lastUpdatedDatetime | The timestamp (in UTC) of the latest action occurring for the borrower out of fields available in this report. Please note, this timestamp only updates if any of the above fields are updated - it does not apply to actions outside this report, so this field does not necessarily correspond to the last time the borrower took action on the loan. If all other timestamp fields are null, this timestamp defaults to the time the borrower user was created (and the borrower may not yet have been invited by the loan officer) | TIMESTAMP_TZ | v5.1.0 | 2/22/2022 | ||||
140 | ||||||||||
141 | ||||||||||
142 | ||||||||||
143 | ||||||||||
144 | Borrower Processes | |||||||||
145 | Reporting Dashboard Report: Borrower Processes | |||||||||
146 | Reporting API Endpoint: Borrower Workflows - https://api.blendlabs.com/reporting/activities | |||||||||
147 | This report is one row per workflow completed by a borrower in their application. You can use it to see where all workflows completed on a loan, or derive a funnel to see where borrowers are dropping off. | |||||||||
148 | ||||||||||
149 | FIELD | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
150 | Activity ID | activityId | PRIMARY KEY - Unique ID of an action completed (e.g. borrower 1 completed assets on loan 1) | STRING | v2.0.0 | 11/1/2019 | ||||
151 | Loan ID | loanId | The UUID of the application in Blend's system. The static identifier that should be used to connect the application's identity across Blend and external integrations | STRING | v2.0.0 | 11/1/2019 | ||||
152 | Loan Reference Number | loanNumber | The unique reference number associated with the loan | STRING | v4.3.0 | 8/24/2021 | ||||
153 | User ID | userId | ID of the user that completed the action (can be a borrower, lender or API user) | STRING | v2.0.0 | 11/1/2019 | ||||
154 | Process Type | type | The name of the workflow completed (e.g. "Getting Started", "Income", etc.) | STRING | v2.0.0 | 11/1/2019 | ||||
155 | Started Datetime | startedDatetime | The timestamp that the user started a workflow | TIMESTAMP_TZ | v2.0.0 | 11/1/2019 | ||||
156 | Completed Datetime | completedDatetime | The timestamp that the user completed a workflow | TIMESTAMP_TZ | v2.0.0 | 11/1/2019 | ||||
157 | ||||||||||
158 | ||||||||||
159 | ||||||||||
160 | ||||||||||
161 | NPS | |||||||||
162 | Reporting Dashboard Report: NPS | |||||||||
163 | Reporting API Endpoint: NPS and Comments - https://api.blendlabs.com/reporting/nps | |||||||||
164 | This report is one row per NPS score submitted on a loan, along with any comments. Use to see trends in feedback from borrowers | |||||||||
165 | ||||||||||
166 | FIELD | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
167 | Loan ID | loanId | PRIMARY KEY - The UUID of the application in Blend's system. The static identifier that should be used to connect the application's identity across Blend and external integrations | STRING | v2.0.0 | 11/1/2019 | ||||
168 | Loan Reference Number | loanNumber | The unique reference number associated with the loan | STRING | v4.3.0 | 8/24/2021 | ||||
169 | NPS Score | score | Borrower assigned NPS score (0-10) | NUMBER | v2.0.0 | 11/1/2019 | ||||
170 | Comment | comment | NPS comment by a borrower | STRING | v2.0.0 | 11/1/2019 | ||||
171 | Datetime | datetime | The timestamp that the borrower submitted the NPS score | TIMESTAMP_TZ | v2.0.0 | 11/1/2019 | ||||
172 | ||||||||||
173 | ||||||||||
174 | ||||||||||
175 | ||||||||||
176 | Follow Ups | |||||||||
177 | Reporting Dashboard Report: Followups | |||||||||
178 | Reporting API Endpoint: Follow-ups Data - https://api.blendlabs.com/reporting/follow-ups | |||||||||
179 | This report is one row per loan with attributes and milestones for that loan. Use it to find things like conversion rate, which apps have not been submitted yet, or where your loan came from. | |||||||||
180 | ||||||||||
181 | FIELD | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
182 | ID | id | PRIMARY KEY - The unique external facing UUID associated with the Follow-up request. | STRING | v5.2.0 | 7/21/2022 | ||||
183 | Follow-Up ID | followUpId | The unique UUID associated with the Follow-up request - primarily for internal Blend Systems use. Use ID field for tying to follow up IDs | STRING | v3.3.0 | 5/26/2020 | ||||
184 | Loan ID | loanId | The UUID of the application in Blend's system. The static identifier that should be used to connect the application's identity across Blend and external integrations. | STRING | v3.3.0 | 5/26/2020 | ||||
185 | Loan Reference Number | loanNumber | The unique reference number associated with the loan | STRING | v4.3.0 | 8/24/2021 | ||||
186 | Loan Type | loanType | The specific product (Mortgage, HELOAN, HELOC, Auto, etc) | STRING | v4.0.0 | 5/26/2020 | ||||
187 | Follow-Up Request Type | requestType | The type of request created the follow-up. Can be AUTOMATED, MANUAL, or SUGGESTED | STRING | v3.3.0 | 5/26/2020 | ||||
188 | Follow-Up Type | followUpType | The type of follow-up requested | STRING | v3.3.0 | 5/26/2020 | ||||
189 | Follow-Up Text | followUpText | Optional text containing additional details about the follow-up. Can be set by Blend, or custom text | STRING | v3.3.0 | 5/26/2020 | ||||
190 | Follow-Up Creation Time | followUpCreatedDatetime | The timestamp the follow-up was created in Blend (field is called followUpCreationTime in Reporting API versions v3.3.0-v4.0.0) | TIMESTAMP_TZ | v3.3.0 | 5/26/2020 | ||||
191 | Client Followup Reference ID | clientFollowupReferenceId | ?? | STRING | v5.1.0 | |||||
192 | Current Status | currentStatus | The current status of the follow-up. Can be Suggested, Declined, Requested, Pending Review, Completed, Completed Externally, Rejected, Cancelled | STRING | v3.3.0 | 5/26/2020 | ||||
193 | Requested Datetime | requestedDatetime | The timestamp the follow-up was requested (field is called requestedAt in Reporting API versions v3.3.0-v4.0.0) | TIMESTAMP_TZ | v3.3.0 | 5/26/2020 | ||||
194 | Requested User ID | requestedUserId | The user_id that requested the follow-up. Can be 'system' or a Lender User ID. Can be tied with Lenders report to get further details on the lender user. | STRING | v3.3.0 | 5/26/2020 | ||||
195 | Requested User Name | requestedUserName | If followup was requested by a Lender user - Full name of the Lender User that requested the follow-up | STRING | v3.3.0 | 5/26/2020 | ||||
196 | Requested User Email | requestedUserEmail | If followup was requested by a Lender user - Email address of the Lender User that requested the follow-up | STRING | v3.3.0 | 5/26/2020 | ||||
197 | Completed Datetime | completedDatetime | The timestamp the follow-up was completed by the borrower (field is called requestedAt in Reporting API versions v3.3.0-v4.0.0) | TIMESTAMP_TZ | v3.3.0 | 5/26/2020 | ||||
198 | Completed User ID | completedUserId | The User ID that completed the follow-up (generally associated with a Borrower) | STRING | v3.3.0 | 5/26/2020 | ||||
199 | Review Action | reviewAction | The action taken by the reviewing lender. Can be ACCEPT or REJECT. | STRING | v3.3.0 | 5/26/2020 | ||||
200 | Reviewed Datetime | reviewedDatetime | The timestamp the follow-up was reviewed (field is called reviewedAt in Reporting API versions v3.3.0-v4.0.0) | TIMESTAMP_TZ | v3.3.0 | 5/26/2020 | ||||
201 | Reviewed User ID | reviewedUserId | The Lender User ID that reviewed the follow-up. Can be tied with Lenders report to get further details on the lender user. | STRING | v3.3.0 | 5/26/2020 | ||||
202 | Cancelled Datetime | cancelledDatetime | The timestamp the follow-up was cancelled (field is called cancelledAt in Reporting API versions v3.3.0-v4.0.0) | TIMESTAMP_TZ | v3.3.0 | 5/26/2020 | ||||
203 | Cancelled User ID | cancelledUserId | The lender User ID that cancelled the follow-up. Can be tied with Lenders report to get further details on the lender user. | STRING | v3.3.0 | 5/26/2020 | ||||
204 | As of Date | asOfDate | The date that the report was generated | TIMESTAMP_TZ | v3.3.0 | 5/26/2020 | ||||
205 | ||||||||||
206 | ||||||||||
207 | ||||||||||
208 | ||||||||||
209 | Data Verification Usage | |||||||||
210 | Reporting Dashboard Report: Data Verification Usage | |||||||||
211 | Reporting API Endpoint: Connectivity Metrics - https://api.blendlabs.com/reporting/data-verification-usage | |||||||||
212 | This table has one row per week, with calculations around data verification usage for that week. Please note this report only includes data on submitted loans. See Application List; /loans endpoint for details on all loans | |||||||||
213 | ||||||||||
214 | FIELD | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
215 | Week | week | The start date of the week | TIMESTAMP_TZ | v3.1.0 | 11/1/2019 | ||||
216 | Total Submits | numberLoansSubmitted | The total number of borrower submitted loans for the week | NUMBER | v3.1.0 | 11/1/2019 | ||||
217 | Number of GAS Generated | numberGasGenerated | Thetotal number of Generated Asset Statements on submitted loans for that week. This only includes instances where a GAS was created from source data in a borrower’s bank account that is eligible for GSE rep and warrant programs (D1C/AIM). GAS does not include successful asset connectivity in cases that Blend is unable to access high enough quality source data for the GSE programs, but will pull a PDF instead and the borrower will not be prompted to upload bank statements (Assets Statement Fallback). | NUMBER | v3.1.0 | 11/1/2019 | ||||
218 | Number of Loans with GAS | numberLoansWithGas | The total number of borrower submitted loans that week that have at least one Generated Asset Statement; this number does not include Asset Statement (PDF) Fallbacks (see description above) | NUMBER | v3.1.0 | 11/1/2019 | ||||
219 | Percent of Loans with GAS | percentSubmitsWithGas | The percent of borrower submitted loans that week that have at least one Generated Asset Statement; this percentage does not include Asset Statement (PDF) Fallbacks (see description above) | NUMBER | v3.1.0 | 11/1/2019 | ||||
220 | Number of Assets Statement Fallback Generated | numberAssetsStatementFallback | The total number of Assets Statement (PDF) Fallbacks created on submitted loans for that week. An Assets Statement Fallback is generated in cases where Blend is unable to access high enough quality source data for the GSE programs to generate a GAS, but will pull a PDF instead and the borrower will not be prompted to upload bank statements; this number does not include Generated Asset Statements (GAS) that are eligible for GSE rep and warrant programs (D1C/AIM). | NUMBER | v5.1.0 | 2/22/2022 | ||||
221 | Number of Loans with Assets Statement Fallback | numberLoansWithAssetsStatementFallback | The total number of borrower submitted loans that week that have at least one Asset Statement (PDF) Fallback; this number does not include Generated Asset Statements (see description above) | NUMBER | v5.1.0 | 2/22/2022 | ||||
222 | Percent of Loans withAssets Statement Fallback | percentSubmitsWithAssetsStatementFallback | The percent of borrower submitted loans that week that have at least one Asset Statement (PDF) Fallback; this number does not include Generated Asset Statements (see description above) | NUMBER | v5.1.0 | 2/22/2022 | ||||
223 | Number of Asset Verification | numberAssetVerification | The total number of Asset Verifications for borrower submitted loans that week, including either Generated Asset Statements (GAS) or Asset Statement Fallbacks (PDF Fallbacks); see descriptions above for details | NUMBER | v5.1.0 | 2/22/2022 | ||||
224 | Number of Loans with Asset Verification | numberLoansWithAssetVerification | The total number of borrower submitted loans that have at least one Asset Verification, including either Generated Asset Statements (GAS) or Asset Statement Fallbacks (PDF Fallbacks); see descriptions above for details | NUMBER | v5.1.0 | 2/22/2022 | ||||
225 | Percent of Loans with Asset Verifications | percentSubmitsWithAssetVerification | The percent of borrower submitted loans that have at least one Asset Verification, including either Generated Asset Statements (GAS) or Asset Statement Fallbacks (PDF Fallbacks); see descriptions above for details | NUMBER | v5.1.0 | 2/22/2022 | ||||
226 | Number of Blend Income Verifications | numberBlendIncomeVerifications | The total number of Blend Income Reports generated on borrower submitted loans in that week | NUMBER | v5.1.0 | 2/22/2022 | ||||
227 | Number of Loans with Blend Income Verification | numberLoansWithBlendIncomeVerification | The total number of borrower submitted loans for that week with at least one Blend Income Verification | NUMBER | v5.1.0 | 2/22/2022 | ||||
228 | Percent of Loans with Blend Income Verification | percentSubmitsWithBlendIncomeVerification | The percent of borrower submitted loans for that week with at least one Blend Income Verification | NUMBER | v5.1.0 | 2/22/2022 | ||||
229 | Total TWN Instant Attempts | numberTwnInstantAttempt | The total number of TWN instant attempts on the previous date | NUMBER | v3.1.0 | 11/1/2019 | ||||
230 | Total TWN Instant Successes | numberTwnInstantSuccess | The total number of TWN instant successes on the previous date | NUMBER | v3.1.0 | 11/1/2019 | ||||
231 | As Of Date | asOfDate | The timestamp (in UTC) for when the report was generated | TIMESTAMP_TZ | v3.1.0 | 11/1/2019 | ||||
232 | ||||||||||
233 | ||||||||||
234 | ||||||||||
235 | ||||||||||
236 | Lenders / Lender User List | |||||||||
237 | Reporting Dashboard Report: Lender User List | |||||||||
238 | Reporting API Endpoint: Lender Users and Usage Metrics - https://api.blendlabs.com/reporting/lenders | |||||||||
239 | This table is one row per lender user, with aggregated counts for various actions during the time period in which you select your date parameters when pullling the report. Please note: If accessing in the Reporting API, the Lenders report behavior is different pre v4.0.0. From v2.0.0-v3.3.0, this report is one row per lender user assigned to each loan, so there will be multiple rows with each lender user if a lender user is assigned to more than one loan. | |||||||||
240 | ||||||||||
241 | FIELD | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
242 | User ID | userid | PRIMARY KEY - Unique User ID associated with the Lender User | STRING | v4.0.0 | 12/17/2020 | ||||
243 | NMLS ID | nmlsId | Lender user's NMLS ID | STRING | v4.0.0 | 12/17/2020 | ||||
244 | Branch ID | branchId | Optional field defined by the client and maintained manually | STRING | v4.0.0 | 12/17/2020 | ||||
245 | Employee ID | employeeId | Optional field defined by the client and maintained manually | STRING | v4.0.0 | 12/17/2020 | ||||
246 | Full Name | fullName | The lender user's full name | STRING | v4.0.0 | 12/17/2020 | ||||
247 | The lender user's email | STRING | v4.0.0 | 12/17/2020 | ||||||
248 | User Roles | userRoles | A list of user roles attributed to the lender | STRING | v4.0.0 | 12/17/2020 | ||||
249 | Lender User LOS Username | losUsername | The lender user's LOS Username in Blend | STRING | v4.0.0 | 12/17/2020 | ||||
250 | Activation Datetime | activationDatetime | When the user accepted Terms of Service | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
251 | Invited Datetime | invitedDatetime | When the account was sent to be activated | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
252 | Last Login Datetime | lastLoginDatetime | Last time the user logged in to their account | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
253 | Total Created Applications | totalCreatedApplications | The total number of created application applications assigned to the lender user. User Metrics timestamp applies to the application creation datetime | NUMBER | v4.0.0 | 12/17/2020 | ||||
254 | Number of Borrower Submits | borrowerSubmits | The total number of loans submitted by the borrower with this lender as the primary assignee. User Metrics date filter applies to borrower application submit datetime for this field | NUMBER | v4.0.0 | 12/17/2020 | ||||
255 | Percent of Loans Submitted | percentLoansSubmitted | The percent of loans submitted out of the total number of created applications assigned to the lender user. The User Metrics date filter applies to the datetime the borrower started the loan for this field. | NUMBER | v4.0.0 | 12/17/2020 | ||||
256 | Percent of Submits with GAS | percentSubmitsWithGas | The percent of borrower submits that have at least one successful Generated Asset Statement on the loan, out of all borrower submits with this lender as the primary assignee. The User Metrics date filter applies to the datetime the borrower started the loan for this field. | NUMBER | v4.0.0 | 12/17/2020 | ||||
257 | Last Submit Timestamp | lastBorrowerSubmitTimestamp | The UTC timestamp for when the last borrower submit was with this lender user as the primary assignee on the loan | NUMBER | v4.0.0 | 12/17/2020 | ||||
258 | Average NPS Score | averageNpsScore | The average NPS score of all submitted applications assigned to the lender user. The User Metrics date filter applies to the NPS submitted datetime for this field. | NUMBER | v4.0.0 | 12/17/2020 | ||||
259 | Calculated NPS Score | calculatedNpsScore | The calculated NPS score for all submitted applications assigned to this lender user. The User Metrics date filter applies to the NPS submitted datetime for this field. | NUMBER | v4.0.0 | 12/17/2020 | ||||
260 | Percent of Loans Utilizing Follow-ups | percentLoansUtilizingFollowups | The percent of the lender user's loans utilizing Follow-ups within the date filters provided. User Metrics date filter field applies to the loan creation datetime for this field | NUMBER | v4.0.0 | 12/17/2020 | ||||
261 | Number of Manually Requested Follow-Ups | followupsManuallyRequested | The number of manually requested Follow-ups by the lender user within the date filters provided. The User Metrics date filter applies to the followup requested datetime for this field | NUMBER | v4.0.0 | 12/17/2020 | ||||
262 | Number of Follow-Ups Completed by Borrower | followupsBorrowerCompleted | The number of Follow-ups completed by the borrower of the loan within the date filters provided. The User Metrics date filter applies to the followup requested datetime for this field. | NUMBER | v4.0.0 | 12/17/2020 | ||||
263 | Number of Follow-Ups Pending | followupsPending | The total number of pending Follow-ups within the date filters provided. The User Metrics date filter applies to the followup requested datetime for this field. | NUMBER | v4.0.0 | 12/17/2020 | ||||
264 | Number of Follow-Ups Accepted | followupsAccepted | The total number of accepted Follow-ups within the date filters provided. The User Metrics date filter applies to the followup requested datetime for this field. | NUMBER | v4.0.0 | 12/17/2020 | ||||
265 | Number of Follow-Ups Rejected | followupsRejected | The total number of rejected Follow-ups within the date filters provided. The User Metrics date filter applies to the followup requested datetime for this field. | NUMBER | v4.0.0 | 12/17/2020 | ||||
266 | As of Date | asOfDate | The timstamp for when the report was generated | TIMESTAMP_TZ | v4.0.0 | 12/17/2020 | ||||
267 | ||||||||||
268 | ||||||||||
269 | ||||||||||
270 | ||||||||||
271 | Deposit Account Applications | |||||||||
272 | Reporting Dashboard Report: Deposit Account Applications | |||||||||
273 | Reporting API Endpoint: Deposit Account Application Data - https://api.blendlabs.com/reporting/deposit-account-applications | |||||||||
274 | This table has one row per Deposit Account application with information on the applications attributes and milestones. | |||||||||
275 | ||||||||||
276 | FIELD | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
277 | Report As Of Datetime | asOfDatetime | UTC datetime of when the data in the report was last refreshed. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
278 | Application Created Datetime | applicationCreatedDatetime | UTC datetime of when the application was created. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
279 | Application ID | applicationId | PRIMARY KEY - UUID of the application in Blend's system. The static identifier that should be used to connect the application's identity across Blend and external integrations. | STRING | v4.3.0 | 7/20/2021 | ||||
280 | Application Reference Number | applicationNumber | Application number displayed in the Blend Workspace. | STRING | v4.3.0 | 7/20/2021 | ||||
281 | Lead Source | leadSource | Type of party that created the application, either "BORROWER" (i.e. the applicant) or "LENDER". | STRING | v4.3.0 | 7/20/2021 | ||||
282 | Application Source Marketing Tag | appSourceMarketingTag | Marketing identifier of the top-of-funnel campaign to which the application should be attributed. | STRING | v4.3.0 | 7/20/2021 | ||||
283 | Applicant Signup URL | applicantSignupUrl | URL of the page through which the primary applicant first created a Blend account. This URL may contain useful referral information if the applicant first arrived at the signup page through a lender-user's custom link or invitation. If there is no URL associated with the primary applicant, this field falls back on the first signup URL associated with the application overall (i.e. that of a coapplicant), if any. | STRING | v5.0.0 | 1/11/2022 | ||||
284 | Is Single App Flow Application | isSingleAppFlowApplication | Boolean indicator for whether the deposit account application was created (and prefilled) via the "Single App Flow" feature, wherein the applicant had actually started by submitting an application for another product, such as a credit card or a loan, for which the applicant must hold a deposit account in order to be eligible. In this situation, the applicant would have been taken from that original application into a new deposit account application with as many fields prefilled as possible based on the applicant's responses in preceding application. | BOOLEAN | v5.0.0 | 1/11/2022 | ||||
285 | Prefill Source Application ID | prefillSourceApplicationId | In the case of a "Single App Flow" application, the application_id of the applicant's previous credit card or loan application from which the new required deposit account application was prefilled. | STRING | v5.0.0 | 1/11/2022 | ||||
286 | Prefill Source Application Type | prefillSourceApplicationType | In the case of a "Single App Flow" application, the product for which the applicant was originally applying, i.e. the product associated with the prefill_source_application_id; for example "Credit Card", "Personal Loan", "Auto Loan", etc. | STRING | v5.0.0 | 1/11/2022 | ||||
287 | Primary Assigned Reviewer User ID | primaryAssignedReviewerUserId | Blend user ID of the application's primary assigned lender-user. | STRING | v4.3.0 | 7/20/2021 | ||||
288 | Primary Assigned Reviewer Full Name | primaryAssignedReviewerFullName | Full name in the primary assigned reviewer's user profile. | STRING | v4.3.0 | 7/20/2021 | ||||
289 | Primary Assigned Reviewer Email | primaryAssignedReviewerEmail | Email address of the primary assigned reviewer. | STRING | v4.3.0 | 7/20/2021 | ||||
290 | Primary Assigned Reviewer Branch ID | primaryAssignedReviewerBranchId | Branch ID in the primary assigned reviewer's user profile. | STRING | v4.3.0 | 7/20/2021 | ||||
291 | Primary Assigned Reviewer Employee ID | primaryAssignedReviewerEmployeeId | Employee ID in the primary assigned reviewer's user profile. | STRING | v4.3.0 | 7/20/2021 | ||||
292 | Primary Assigned Reviewer Nmls ID | primaryAssignedReviewerNmlsId | Nationwide Multistate Licensing System ID in the primary assigned reviewer's user profile. | STRING | v4.3.0 | 7/20/2021 | ||||
293 | Product Bundle Reference ID | productBundleReferenceId | Product bundle ID associated with the application (a single application can open multiple accounts, e.g. "Checking & Savings"). | STRING | v4.3.0 | 7/20/2021 | ||||
294 | Total Number of Accounts in Bundle | totalNumberofAccountsInBundle | Number of accounts in the product bundle that will be opened if the application is approved. | NUMBER | v4.3.0 | 7/20/2021 | ||||
295 | Debit Card Selected | debitCardSelected | Boolean indicator for whether the applicant opted in for a debit card. | BOOLEAN | v4.3.0 | 7/20/2021 | ||||
296 | Overdraft Protection Selected | overdraftProtectionSelected | Boolean indicator for whether the applicant opted in for overdraft protection. | BOOLEAN | v4.3.0 | 7/20/2021 | ||||
297 | Number of Checking Accounts | numberOfCheckingAccounts | Number of checking accounts in the product bundle that will be opened if the application is approved. | NUMBER | v4.3.0 | 7/20/2021 | ||||
298 | Checking Product Reference IDs | checkingProductReferenceIds | Product ID(s) of the specific checking product(s) in the bundle; may be the same as the product_bundle_reference_id if the application is for a single checking account. This field will contain a comma-separated list of IDs when the application is for a multi-account bundle containing more than one checking account. | STRING | v4.3.0 | 7/20/2021 | ||||
299 | Checking Product Names | checkingProductNames | Full humanized name(s) of the checking product(s) in the bundle. This field will contain a comma-separated list of names when the application is for a multi-account bundle with more than one checking account. | STRING | v4.3.0 | 7/20/2021 | ||||
300 | Number of Savings Accounts | numberOfSavingsAccounts | Number of savings accounts in the product bundle that will be opened if the application is approved. | NUMBER | v4.3.0 | 7/20/2021 | ||||
301 | Savings Product Reference IDs | savingsProductReferenceIds | Product ID(s) of the specific savings product(s) in the bundle; may be the same as the product_bundle_reference_id if the application is for a single savings account. This field will contain a comma-separated list of IDs when the application is for a multi-account bundle containing more than one savings account. | STRING | v4.3.0 | 7/20/2021 | ||||
302 | Savings Product Names | savingsProductNames | Full humanized name(s) of the savings product(s) in the bundle. This field will contain a comma-separated list of names when the application is for a multi-account bundle with more than one savings account. | STRING | v4.3.0 | 7/20/2021 | ||||
303 | Number of CD Accounts | numberofCdAccounts | Number of certificates of deposit (CDs) in the product bundle that will be opened if the application is approved. | NUMBER | v4.3.0 | 7/20/2021 | ||||
304 | CD Product Reference IDs | cdProductReferenceIds | Product ID(s) of the specific CD product(s) in the bundle; may be the same as the product_bundle_reference_id if the application is for a single CD. This field will contain a comma-separated list of identifiers when the application is for a multi-account bundle containing more than one CD. | STRING | v4.3.0 | 7/20/2021 | ||||
305 | CD Product Names | cdProductNames | Full humanized name(s) of the CD product(s) in the bundle. This field will contain a comma-separated list of names when the application is for a multi-account bundle with more than one CD. | STRING | v4.3.0 | 7/20/2021 | ||||
306 | CD Terms | cdTerms | Chosen term length(s) of the CD(s) in the bundle, appearing as strings such as "12_MONTHS" and "36_MONTHS". This field will contain a comma-separated list of term lengths when the application is for a multi-account bundle with more than one CD. | STRING | v4.3.0 | 7/20/2021 | ||||
307 | Number of HSA Accounts | numberofHsaAccounts | Number of health savings accounts (HSAs) in the product bundle that will be opened if the application is approved. | NUMBER | v4.3.0 | 7/20/2021 | ||||
308 | HSA Product Reference IDs | hsaProductReferenceIds | Product ID(s) of the specific HSA product(s) in the bundle; may be the same as the product_bundle_reference_id if the application is for a single HSA. This field will contain a comma-separated list of identifiers when the application is for a multi-account bundle containing more than one HSA. | STRING | v4.3.0 | 7/20/2021 | ||||
309 | HSA Product Names | hsaProductNames | Full humanized name(s) of the health savings account (HSA) product(s) in the bundle. This field will contain a comma-separated list of names when the application is for a multi-account bundle with more than one HSA. | STRING | v4.3.0 | 7/20/2021 | ||||
310 | HSA Plan Types | hsaPlanTypes | Chosen plan type(s) of the HSA(s) in the bundle, either "INDIVIDUAL" or "FAMILY". This field will contain a comma-separated list of plan types when the application is for a multi-account bundle with more than one HSA. | STRING | v4.3.0 | 7/20/2021 | ||||
311 | Total Number of Applicants | totalNumberOfApplicants | Number of applicants on the application (primary, co-, and minor applicants). | NUMBER | v4.3.0 | 7/20/2021 | ||||
312 | Number of Primary Applicants | numberOfPrimaryApplicants | Number of primary applicants on the application. Every application should have one primary applicant. | NUMBER | v4.3.0 | 7/20/2021 | ||||
313 | Primary Applicant Employment Status | primaryApplicantEmploymentStatus | Employment status of the primary applicant. There are five statuses the applicant can choose from, including "EMPLOYED", "SELF_EMPLOYED", "UNEMPLOYED", "RETIRED", and "NEVER_EMPLOYED". | STRING | v4.3.0 | 7/20/2021 | ||||
314 | Primary Applicant is Existing Member | primaryApplicantIsExistingMember | Boolean indicator that is TRUE if either the member lookup call returned a match for the primary applicant in the core banking system, or the primary applicant self-indicated that they are an existing member of the institution if asked in the application. | BOOLEAN | v4.3.0 | 7/20/2021 | ||||
315 | Number of Coapplicants | numberOfCoapplicants | Number of coapplicants on the application. | NUMBER | v4.3.0 | 7/20/2021 | ||||
316 | Coapplicant Employment Status | coapplicantEmploymentStatus | Employment status of the coapplicant. There are five statuses the coapplicant can choose from, including "EMPLOYED", "SELF_EMPLOYED", "UNEMPLOYED", "RETIRED", and "NEVER_EMPLOYED". | STRING | v4.3.0 | 7/20/2021 | ||||
317 | Coapplicant is Existing Member | coapplicantIsExistingMember | Boolean indicator that is TRUE if the member lookup call returned a match for the coapplicant in the core banking system. | BOOLEAN | v5.2.0 | 7/14/2022 | ||||
318 | Number of Minor Applicants | numberOfMinorApplicants | Number of minor applicants (i.e. persons under 18) on the application. | NUMBER | v4.3.0 | 7/20/2021 | ||||
319 | First UI Tracking Event Datetime | firstUiTrackingEventDatetime | UTC datetime of the first tracking event associated with the application. The presence of an event should indicate that the applicant at least allowed the UI to load. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
320 | First Minor Info Workflow Event Datetime | firstMinorInfoWorkflowEventDatetime | UTC datetime of the first tracking event in the "Minor Info" workflow. | TIMESTAMP_TZ | v5.0.0 | 1/11/2022 | ||||
321 | First Personal Info Workflow Event Datetime | firstPersonalInfoWorkflowEventDatetime | UTC datetime of the first tracking event in the "Personal Info" workflow | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
322 | Has Activity Beyond Initial Details Task | hasActivityBeyondInitialDetailsTask | Boolean indicator compiling all possible downfunnel evidence that the application made it past the initial "Get Applicant Details" task in the "Personal Info" workflow. The field is intended to be used as a more qualified definition of "started", with a value of TRUE identifying applications that were not abandoned on the first page. | BOOLEAN | v4.3.0 | 7/20/2021 | ||||
323 | Device Type Start | deviceTypestart | The type of device ("Desktop", "Mobile", or "Tablet") used for the application's first user action, which should correspond to clicking "continue" on the first page of the application. | STRING | v4.3.0 | 7/20/2021 | ||||
324 | First IDV Workflow Event Datetime | firstIdvWorkflowEventDatetime | UTC datetime of the first tracking event in the "Identity Verfication" workflow. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
325 | First IDV Workflow Submit Datetime | firstIdvWorkflowSubmitDatetime | UTC datetime of the first click on "Submit and Continue" on the final page of the "Identity Verification" workflow, which should submit the applicant's information to the third-party identity verification (IDV) provider (Alloy or Socure). The exception to this is when the applicant is an existing member of the institution, and the institution has configured its application to "offboard" existing members from the application without submission to the IDV provider. | TIMESTAMP_TZ | v5.0.0 | 1/11/2022 | ||||
326 | First IDV Workflow Additional Info Requested Datetime | firstIdvWorkflowAdditionalInfoRequestedDatetime | UTC datetime of the first time an applicant was sent to the supplementary "Step Up" task in the "Identity Verification" workflow, where additional identifying information is requested, if the initial ID information provided was found to be insufficient for evaluation/decisioning. | TIMESTAMP_TZ | v5.0.0 | 1/11/2022 | ||||
327 | First Account Setup Workflow Event Datetime | firstAccountSetupWorkflowEventDatetime | UTC datetime of the first tracking event in the "Account Setup" workflow. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
328 | Has Beneficiaries Added | hasBeneficiariesAdded | Boolean indicator for whether any beneficiaries were specified and allocated for the new account(s) in the "Account Setup" workflow. | BOOLEAN | v4.3.0 | 7/20/2021 | ||||
329 | Application Submitted Datetime | applicationSubmittedDatetime | UTC datetime of application submission. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
330 | Application Submission Status | applicationSubmissionStatus | Supplementary status indicator that may be able to confirm application submission even in the case of a lapse in the event tracking that produces application_submitted_datetime; either "SUBMITTED" or "NOT SUBMITTED". | STRING | v4.3.0 | 7/20/2021 | ||||
331 | Total Number of Follow-Ups Requested | totalNumberOfFollowupsRequested | Number of follow-up tasks requested of the applicant by a lender-user through Blend's "Follow-Ups" tool. | NUMBER | v5.0.0 | 1/11/2022 | ||||
332 | First Automated Approval Datetime | firstAutomatedApprovalDatetime | UTC datetime of the first automated approval decision on the application emitted by the third-party identity verification (IDV) provider (Alloy or Socure). An approval decision will not be emitted unless and until the application is submitted. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
333 | First Automated Referral Datetime | firstAutomatedReferralDatetime | UTC datetime of the first automated referral on the application, where the third-party identity verification (IDV) provider (Alloy or Socure) flags the application for manual review by a lender-user. A referral decision will not be made unless and until the application is submitted. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
334 | First Automated Rejection Datetime | firstAutomatedRejectionDatetime | UTC datetime of the first automated rejection decision by the third-party identity verification (IDV) provider (Alloy or Socure) or by the "system" (i.e. application configurations set by the institution to reject/"offboard" certain applicants, like existing members, on the spot). A rejection decision can be emitted prior to application submission if the applicant fails the basic preliminary IDV screening (because of a low Qualifile score) and triggers an "adverse action notice" (AAN) in the "Identity Verification" workflow, or if they are rejected by system rules. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
335 | First Automated Rejection Source | firstAutomatedRejectionSource | Source of the first automated rejection decision, either "IDV provider" (Alloy or Socure) or "system" (i.e. application configurations set by the institution to reject/"offboard" certain applicants, like existing members, on the spot). | STRING | v5.0.0 | 1/11/2022 | ||||
336 | Primary Applicant Rejected via Adverse Action Notice | primaryApplicantRejectedViaAan | Booelan indicator for whether the primary applicant was rejected via "adverse action notice" (AAN) based on their "Qualifile" score in the "Identity Verification" workflow, which would result in an immediate rejection of the application without proceeding to the "Account Setup" workflow. If the applicant has not yet submitted their information for IDV evaulation, this field will be null. | BOOLEAN | v5.0.0 | 1/11/2022 | ||||
337 | Coapplicant Rejected via Adverse Action Notice | coapplicantRejectedViaAan | Booelan indicator for whether the coapplicant was rejected via "adverse action notice" (AAN) based on their "Qualifile" score in the "Identity Verification" workflow. If there is no coapplicant on the application, or the coapplicant has not yet submitted their information for IDV evaulation, this field will be null. | BOOLEAN | v5.0.0 | 1/11/2022 | ||||
338 | First Manual Approval Datetime | firstManualApprovalDatetime | UTC datetime of the first manual approval decision on the application issued by a lender-user. An application cannot be reviewed or approved unless and until the application is submitted. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
339 | First Manual Approval Reviewer User ID | firstManualApprovalReviewerUserId | Blend user ID of the lender-user who manually approved the application. | STRING | v4.3.0 | 7/20/2021 | ||||
340 | First Manual Approval Reviewer Full Name | firstManualApprovalReviewerFullName | Full name in the user profile of the lender-user who manually approved the application. | STRING | v4.3.0 | 7/20/2021 | ||||
341 | First Manual Approval Reviewer Email | firstManualApprovalReviewerEmail | Email address of the lender-user who manually approved the application. | STRING | v4.3.0 | 7/20/2021 | ||||
342 | First Manual Approval Reviewer Branch ID | firstManualApprovalReviewerBranchId | Branch ID in the user profile of the lender-user who manually approved the application. | STRING | v4.3.0 | 7/20/2021 | ||||
343 | First Manual Approval Reviewer Employee ID | firstManualApprovalReviewerEmployeeId | Employee ID in the user profile of the lender-user who manually approved the application. | STRING | v4.3.0 | 7/20/2021 | ||||
344 | First Manual Approval Reviewer Nmls ID | firstManualApprovalReviewerNmlsId | Nationwide Multistate Licensing System ID in the user profile of the lender-user who manually approved the application. | STRING | v4.3.0 | 7/20/2021 | ||||
345 | First Manual Rejection Datetime | firstManualRejectionDatetime | UTC datetime of the first manual rejection decision on the application issued by a lender-user. An application cannot be reviewed or rejected unless and until the application is submitted. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
346 | First Manual Rejection Reviewer User ID | firstManualRejectionReviewerUserId | Blend user ID of the lender-user who manually rejected the application. | STRING | v4.3.0 | 7/20/2021 | ||||
347 | First Manual Rejection Reviewer Full Name | firstManualRejectionReviewerFullName | Full name in the user profile of the lender-user who manually rejected the application. | STRING | v4.3.0 | 7/20/2021 | ||||
348 | First Manual Rejection Reviewer Email | firstManualRejectionReviewerEmail | Email address of the lender-user who manually rejected the application. | STRING | v4.3.0 | 7/20/2021 | ||||
349 | First Manual Rejection Reviewer Branch ID | firstManualRejectionReviewerBranchId | Branch ID in the user profile of the lender-user who manually rejected the application. | STRING | v4.3.0 | 7/20/2021 | ||||
350 | First Manual Rejection Reviewer Employee ID | firstManualRejectionReviewerEmployeeId | Employee ID in the user profile of the lender-user who manually rejected the application. | STRING | v4.3.0 | 7/20/2021 | ||||
351 | First Manual Rejection Reviewer Nmls ID | firstManualRejectionReviewerNmlsId | Nationwide Multistate Licensing System ID in the user profile of the lender-user who manually rejected the application. | STRING | v4.3.0 | 7/20/2021 | ||||
352 | Latest Decision Datetime | latestDecisionDatetime | UTC datetime of the latest decision on the application, automated or manual, approval or rejection. See descriptions of first_automated_approval_datetime, first_automated_rejection_datetime, first_manual_approval_datetime, and first_manual_rejection_datetime for detail on each decision type and outcome. Referrals are not considered true "decisions" and thus are ignored by this field. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
353 | Latest Decision Type | latestDecisionType | Type, either "automated" or "manual", of the latest decision on the appliction, approval or rejection. Referrals are not considered true "decisions" and thus are ignored by this field. | STRING | v4.3.0 | 7/20/2021 | ||||
354 | Latest Decision Outcome | latestDecisionOutcome | Outcome, either "approve" or "reject", of the latest decision on the application, automated or manual. Referrals are not considered true "decisions" and thus are ignored by this field. | STRING | v4.3.0 | 7/20/2021 | ||||
355 | Latest Decision Automated Rejection Source | latestDecisionAutomatedRejectionSource | If the latest decision on the application is an automated rejection, the source of that rejection, either "IDV provider" (Alloy or Socure) or "system" (i.e. application configurations set by the institution to reject/"offboard" certain applicants, like existing members, on the spot). | STRING | v5.0.0 | 7/20/2021 | ||||
356 | Latest Decision Reviewer User ID | latestDecisionReviewerUserId | If the latest decision on the application is manual, the Blend user ID of the lender-user who made that decision. | STRING | v4.3.0 | 7/20/2021 | ||||
357 | Latest Decision Reviewer Full Name | latestDecisionReviewerFullName | If the latest decision on the application is manual, the full name in the user profile of the lender-user who made that decision. | STRING | v4.3.0 | 7/20/2021 | ||||
358 | Latest Decision Reviewer Email | latestDecisionReviewerEmail | If the latest decision on the application is manual, the email address of the lender-user who made that decision. | STRING | v4.3.0 | 7/20/2021 | ||||
359 | Latest Decision Reviewer Branch ID | latestDecisionReviewerBranchId | If the latest decision on the application is manual, the branch ID in the user profile of the lender-user who made that decision. | STRING | v4.3.0 | 7/20/2021 | ||||
360 | Latest Decision Reviewer Employee ID | latestDecisionReviewerEmployeeId | If the latest decision on the application is manual, the employee ID in the user profile of the lender-user who made the decision. | STRING | v4.3.0 | 7/20/2021 | ||||
361 | Latest Decision Reviewer Nmls ID | latestDecisionReviewerNmlsId | If the latest decision on the application is manual, the Nationwide Multistate Licensing System ID in the user profile of the lender-user who made that latest decision. | STRING | v4.3.0 | 7/20/2021 | ||||
362 | Application Approval Status | applicationApprovalStatus | Approval status of the application, either "APPROVED", "REFERRED", or "REJECTED" if the application has reached a decisioning point, or null if not. | STRING | v4.3.0 | 7/20/2021 | ||||
363 | Account Booked To Core Datetime | accountBookedToCoreDatetime | UTC datetime that the newly opened account(s) was successfully booked to the institution's core banking system. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
364 | Application Booking Status | applicationBookingStatus | Supplementary status indicator that may be able to confirm that the newly opened account(s) was successfully booked even in the case of a lapse in the event tracking that produces account_booked_to_core_datetime; either "BOOKED" or null. | STRING | v4.3.0 | 7/20/2021 | ||||
365 | First Funding Workflow Event Datetime | firstFundingWorkflowEventDatetime | UTC datetime of the first tracking event in the "Opening Deposit" workflow. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
366 | First Opening Deposit Transaction Submitted Datetime | firstOpeningDepositTransactionSubmittedDatetime | UTC datetime of the first deposit transaction submitted through the "Opening Deposit" workflow. The exception to this is for institutions that have configured their application to preemptively require the applicant to complete the opening deposit tasks in the "Account Setup" workflow prior to application submission, in which case this field will still report a datetime once those tasks have been completed, even if the application was never subsequently submitted, approved, and booked to the core banking system, and accordingly no opening deposits were actually transferred. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
367 | Number of New Accounts Funded | numberOfNewAccountsFunded | Number of newly opened accounts funded with an initial deposit submitted through the "Opening Deposit" workflow. The exception to this is for institutions that have configured their application to preemptively require the applicant to complete the opening deposit tasks in the "Account Setup" workflow prior to application submission, in which case this field will still report the number of intended desintation accounts once those tasks have been completed, even if the application was never subsequently submitted, approved, and booked to the core banking system, and accordingly no opening deposits were actually transferred. | NUMBER | v4.3.0 | 7/20/2021 | ||||
368 | Opening Deposit Amounts | openingDepositAmounts | Dollar amount(s) of the opening deposit(s) submitted through the "Opening Deposit" workflow, rounded to the nearest increment of 50. This field will contain a comma-separated list of amounts when multiple newly opened accounts that originated from the same application were funded. The exception to this is for institutions that have configured their application to preemptively require the applicant to complete the opening deposit tasks in the "Account Setup" workflow prior to application submission, in which case this field will still report the intended deposit amount(s) once those tasks have been completed, even if the application was never subsequently submitted, approved, and booked to the core banking system, and accordingly no opening deposits were actually transferred. | STRING | v4.3.0 | 7/20/2021 | ||||
369 | Total Amount Deposited | totalAmountDeposited | Sum of the dollar amounts (each rounded to the nearest increment of 50 prior to summation) of the opening deposits submitted through the "Opening Deposit" workflow; the sum will be the same as the value in opening_deposit_amounts if only one new account was funded. The exception to this is for institutions that have configured their application to preemptively require the applicant to complete the opening deposit tasks in the "Account Setup" workflow prior to application submission, in which case this field will still report the intended total deposit amount once those tasks have been completed, even if the application was never subsequently submitted, approved, and booked to the core banking system, and accordingly no opening deposits were actually transferred. | FLOAT | v4.3.0 | 7/20/2021 | ||||
370 | Opening Deposit Source Account Connection Method | openingDepositSourceAccountConnectionMethod | Method used to connect an external source account for the transfer of an opening deposit in the "Opening Deposit" workflow. The applicant can either use the Plaid integration to log in to a financial institution, or manually enter the account and routing numbers of the source account. This field will have a value of either "Plaid", "manual entry", or "unknown" when first_opening_deposit_transaction_submitted_datetime is populated, and null otherwise. The exception to this is for institutions that have configured their application to preemptively require the applicant to complete the opening deposit tasks in the "Account Setup" workflow prior to application submission, in which case this field will still report the chosen connection method once those tasks have been completed, even if the application was never subsequently submitted, approved, and booked to the core banking system, and accordingly no opening deposits were actually transferred. | STRING | v5.0.0 | 1/11/2022 | ||||
371 | Opening Deposit Source Account Type | openingDepositSourceAccountType | Type of source account used to fund the opening deposit, either "checking", "savings", or "unknown". The account type (checking or savings) is known for all Plaid-connected source accounts, whereas this information is only collected for manually entered source accounts if the instutition has configured the application to ask the applicant to specify the account type. The exception to this is for institutions that have configured their application to preemptively require the applicant to complete the opening deposit tasks in the "Account Setup" workflow prior to application submission, in which case this field will still report the intended source account type once those tasks have been completed, even if the application was never subsequently submitted, approved, and booked to the core banking system, and accordingly no opening deposits were actually transferred. | STRING | v5.0.0 | 1/11/2022 | ||||
372 | Application Funding Status | applicationFundingStatus | Funding status of the application. This field will be "FUNDED VIA BLEND" if an opening deposit for at least one newly opened account was submitted through the "Opening Deposit" workflow (i.e. if application_booking_status = "BOOKED" and first_opening_deposit_transaction_submitted_datetime exists), and null otherwise. | STRING | v4.3.0 | 7/20/2021 | ||||
373 | Application Status Overall | applicationStatusOverall | Overall latest status of the application (i.e. the most down-funnel status reached to date), either "NOT SUBMITTED", "SUBMITTED", "REFERRED", "APPROVED", "REJECTED", "BOOKED", or "FUNDED VIA BLEND". | STRING | v4.3.0 | 7/20/2021 | ||||
374 | First Online Banking Registration Workflow Event Datetime | firstOnlineBankingRegistrationWorkflowEventDatetime | UTC datetime of the first tracking event in the "Online Banking Registration" workflow. | TIMESTAMP_TZ | v5.0.0 | 1/11/2022 | ||||
375 | Online Banking Registration Completed Datetime | onlineBankingRegistrationCompletedDatetime | UTC datetime of when the new account holder succesfully created and submitted login credentials for online banking access at the institution via the "Online Banking Registration" workflow. | TIMESTAMP_TZ | v5.0.0 | 1/11/2022 | ||||
376 | Application Last Touch Datetime | applicationLateTouchDatetime | UTC datetime of when the application was last touched (by either an applicant or a lender-user). | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
377 | Application Last Touched By User ID | applicationLastTouchedByUserId | Blend user ID of the applicant or lender-user who last touched the application. | STRING | v4.3.0 | 7/20/2021 | ||||
378 | Application Last Updated Datetime | applicationLastUpdatedDatetime | UTC datetime of when the application record was last updated by the system. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
379 | Application Archived Datetime | applicationArchivedDatetime | UTC datetime of when the application was archived in Blend. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
380 | Application Deleted Datetime | applicationDeletedDatetime | UTC datetime of when the application was deleted by a user. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
381 | Application Purged Datetime | applicationPurgedDatetime | UTC datetime of when the application was purged from Blend production. | TIMESTAMP_TZ | v4.3.0 | 7/20/2021 | ||||
382 | ||||||||||
383 | ||||||||||
384 | ||||||||||
385 | ||||||||||
386 | Configurable Products - Applications | |||||||||
387 | Reporting Dashboard Report: Configurable Products - Applications | |||||||||
388 | Reporting API Endpoint: Configurable Products Applications Data - https://api.beta.blendlabs.com/reporting/configurable-products-applications | |||||||||
389 | This table has one row per application for all products built on Blend's Configurable Platform. | |||||||||
390 | ||||||||||
391 | FIELD | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
392 | Report As Of Datetime | asOfDatetime | UTC datetime of when the data in the report was last refreshed. | TIMESTAMP_TZ | v5.0.0 | 2/8/2022 | ||||
393 | Product Name | productName | Text name of the product for which the applicant is applying, as defined by the application developer. | STRING | v5.0.0 | 2/8/2022 | ||||
394 | Application Created Datetime | applicationCreatedDatetime | UTC datetime of when the application was created. | TIMESTAMP_TZ | v5.0.0 | 2/8/2022 | ||||
395 | Application ID | applicationId | PRIMARY KEY - UUID of the application in Blend's system. The static identifier that should be used to connect the application's identity across Blend and external integrations. | STRING | v5.0.0 | 2/8/2022 | ||||
396 | Application Reference Number | applicationNumber | Application number displayed in the Blend Workspace. | STRING | v5.0.0 | 2/8/2022 | ||||
397 | Primary Assignee User ID | primaryAssigneeUserId | Blend user ID of the application's primary assigned lender-user. | STRING | v5.0.0 | 2/8/2022 | ||||
398 | Primary Assignee Full Name | primaryAssigneeFullName | Full name in the primary assignee's user profile. | STRING | v5.0.0 | 2/8/2022 | ||||
399 | Primary Assignee Email | primaryAssigneeEmail | Email address of the primary assignee. | STRING | v5.0.0 | 2/8/2022 | ||||
400 | Primary Assignee Branch ID | primaryAssigneeBranchId | Branch ID in the primary assignee's user profile. | STRING | v5.0.0 | 2/8/2022 | ||||
401 | Primary Assignee Employee ID | primaryAssigneeEmployeeId | Employee ID in the primary assignee's user profile. | STRING | v5.0.0 | 2/8/2022 | ||||
402 | Application Deletion Datetime | applicationDeletionDatetime | UTC datetime of when the application was deleted from Blend's production database, either manually by a user or automatically. | TIMESTAMP_TZ | v6.0.0 | 1/31/2023 | ||||
403 | Application Deletion Type | applicationDeletionType | The method by which the application was deleted from Blend, either "MANUAL" or "AUTOMATIC". | STRING | v6.0.0 | 1/31/2023 | ||||
404 | ||||||||||
405 | ||||||||||
406 | ||||||||||
407 | ||||||||||
408 | Configurable Products - Application Node History | |||||||||
409 | Reporting Dashboard Report: Configurable Products - Application Node History | |||||||||
410 | Reporting API Endpoint: N/A | |||||||||
411 | This table has one row per node reached per application for all products built on Blend's Configurable Platform. (A "node" is essentially a page or decisioning point or integration call defined in an application template by its developer, and a unique "node instance" is created when an individual application reaches each node in the workflow.) | |||||||||
412 | ||||||||||
413 | FIELD | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
414 | Report As Of Datetime | asOfDatetime | UTC datetime of when the data in the report was last refreshed. | TIMESTAMP_TZ | N/A | 2/8/2022 | ||||
415 | Product Name | productName | Text name of the product for which the applicant is applying, as defined by the application developer. | STRING | N/A | 2/8/2022 | ||||
416 | Application Created Datetime | applicationCreatedDatetime | UTC datetime of when the application was created. | TIMESTAMP_TZ | N/A | 2/8/2022 | ||||
417 | Application ID | applicationId | UUID of the application in Blend's system. The static identifier that should be used to connect the application's identity across Blend and external integrations. | STRING | N/A | 2/8/2022 | ||||
418 | Applicant User ID | applicantUserId | Identifier of the applicant associated with the node instance. For products that can have joint applicants, each of which could log in and contribute to the application separately, an application could have multiple instances of the same node associated with different applicant_user_ids. | STRING | N/A | 2/8/2022 | ||||
419 | Node Name | nodeName | Text name of the node that the application reached, as defined by the application developer. | STRING | N/A | 2/8/2022 | ||||
420 | Node Type | nodeType | The descriptive function classification of the node that the application reached: LINKED_PAGE, LINKED_LOOP, LINKED_ENABLEMENT, LINKED_INTEGRATION, LINKED_PARALLELIZATION, LINKED_REVIEW, LINKED_EVENT DECISION, or LINKED_EMAIL. | STRING | N/A | 2/8/2022 | ||||
421 | Node Instance Created Datetime | nodeInstanceCreatedDatetime | The datetime of when the application first encountered the node, thereby creating the new node instance. For exmaple, for a node that governs a page in the application UI (i.e. where node_type = 'LINKED_PAGE'), node_instance_created_datetime would correspond to when the applicant first saw the page. | TIMESTAMP_TZ | N/A | 2/8/2022 | ||||
422 | Node Instance First Completed Datetime | nodeInstanceFirstCompletedDatetime | The datetime of when the application first completed the node's task/process, if ever. For exmaple, for a node that governs a page in the application UI (i.e. where node_type = 'LINKED_PAGE'), node_instance_first_completed_at would correspond to when the applicant first submitted the page. CAUTION: This tracking was not implemented until Jan. 7, 2022, and therefore nodes completed prior to that date will not have a datetime populated in this field. | TIMESTAMP_TZ | N/A | 2/8/2022 | ||||
423 | ||||||||||
424 | ||||||||||
425 | ||||||||||
426 | ||||||||||
427 | Configurable Products - Application Field Inputs | |||||||||
428 | Reporting Dashboard Report: Configurable Products - Application Field Inputs | |||||||||
429 | Reporting API Endpoint: N/A | |||||||||
430 | This table has one row per field submitted per application for all products built on Blend's Configurable Platform, if (1) that field has been mapped to a standardized field defintion in the application template and (2) that standardized field defintion has been approved for ingestion and storage in Blend's data warehouse under PII retention policies. | |||||||||
431 | ||||||||||
432 | FIELD | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
433 | Report As Of Datetime | asOfDatetime | UTC datetime of when the data in the report was last refreshed. | TIMESTAMP_TZ | N/A | 1/20/2023 | ||||
434 | Product Name | productName | Text name of the product for which the applicant is applying, as defined by the application developer. | STRING | N/A | 1/20/2023 | ||||
435 | Application Created Datetime | applicationCreatedDatetime | UTC datetime of when the application was created. | TIMESTAMP_TZ | N/A | 1/20/2023 | ||||
436 | Application ID | applicationId | UUID of the application in Blend's system. The static identifier that should be used to connect the application's identity across Blend and external integrations. | STRING | N/A | 1/20/2023 | ||||
437 | Field Name | fieldName | Text name of the field in the application template, as defined by the application developer. | STRING | N/A | 1/20/2023 | ||||
438 | Field Data Type | fieldDataType | The type of input taken by the field, either 'NUMBER' or 'STRING' currently. | STRING | N/A | 1/20/2023 | ||||
439 | Field Number Value | fieldNumberValue | The field input value for fields of data type 'NUMBER'. | NUMBER | N/A | 1/20/2023 | ||||
440 | Field String Value | fieldStringValue | The field input value for fields of data type 'STRING'. | STRING | N/A | 1/20/2023 | ||||
441 | Field Boolean Value | fieldBooleanValue | The "true"/"false" value to which the field has been set for fields of data type 'BOOLEAN'. Most boolean fields are invisible to the applicant and are set automatically by application's backend logic, rather than by the applicant manually selecting a "true"/"false" response to a field in the frontend application UI. | BOOLEAN | N/A | 4/3/2023 | ||||
442 | Field Value Last Updated Datetime | fieldValueLastUpdatedDatetime | The datetime of when the field input was last updated. | TIMESTAMP_TZ | N/A | 1/20/2023 | ||||
443 | ||||||||||
444 | ||||||||||
445 | ||||||||||
446 | ||||||||||
447 | Closings | |||||||||
448 | Reporting Dashboard Report: Closings | |||||||||
449 | Reporting API Endpoint: N/A | |||||||||
450 | This report is one row per Blend Close with data on different attributes | |||||||||
451 | ||||||||||
452 | FIELD LONG NAME | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
453 | Loan Reference Number | loanNumber | The unique reference number associated with the loan | STRING | N/A | 5/10/2022 | ||||
454 | Application Id | applicationId | PRIMARY KEY - Unique ID of the activity | STRING | N/A | 5/10/2022 | ||||
455 | Loan Type | loanType | The specific product (Mortgage, HELOAN, HELOC, Auto, etc) | STRING | N/A | 5/10/2022 | ||||
456 | Closing Type | closingType | Closing type. Options are TRADITIONAL, RON, HYBRID, or UNDETERMINED | STRING | N/A | 5/10/2022 | ||||
457 | First Sent To Borrower Timestamp | firstSentToBorrowerDatetime | Timestamp (in UTC) for when the Close was first sent to the borrower | TIMESTAMP_TZ | N/A | 5/10/2022 | ||||
458 | Esign Period Start Timestamp | esignPeriodStartDatetime | Timestamp (in UTC) for when the esign period started | TIMESTAMP_TZ | N/A | 5/10/2022 | ||||
459 | Esign Period End Timestamp | esignPeriodEndDatetime | Timestamp (in UTC) for when the esign period ended | TIMESTAMP_TZ | N/A | 5/10/2022 | ||||
460 | ||||||||||
461 | ||||||||||
462 | ||||||||||
463 | ||||||||||
464 | ||||||||||
465 | Title Documents | |||||||||
466 | Reporting Dashboard Report: Title Documents | |||||||||
467 | Reporting API Endpoint: N/A | |||||||||
468 | This is a temporary table that is a subset of documents related to Blend Title orders along with associated title information. It will not be added to the Reporting API in the foreseeable future. | |||||||||
469 | ||||||||||
470 | FIELD LONG NAME | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
471 | Document ID | documentId | PRIMARY KEY - Unique ID of the document | STRING | N/A | 5/24/2022 | ||||
472 | Loan ID | loanID | The UUID of the application in Blend's system. The static identifier that should be used to connect the application's identity across Blend and external integrations | STRING | N/A | 5/24/2022 | ||||
473 | Loan Number | loanNumber | The unique reference number associated with the loan | STRING | N/A | 5/24/2022 | ||||
474 | Uploaded By User Type | uploadedByUserType | The type of user that uploaded the document. Can be one of the following: system = Documents automatically uploaded by Blend (e.g. asset statements, compliance reports, etc) external_api = Documents uploaded to Blend through the public API by a third party (e.g. Disclosures, Document Signature Requests, etc.) internal_api = Additional Blend services may appear as using the internal API to upload documents (e.g. Verification of Income, Pre Approval Letters, etc) borrower = uploaded by a borrower lender = uploaded by a lender user" | STRING | N/A | 5/24/2022 | ||||
475 | Document Type | type | The type of document uploaded | STRING | N/A | 5/24/2022 | ||||
476 | Document Source | documentSource | The source of where the document came from. Can be 'connectivity' for documents pulled through Blend's connectivity, or 'user' for all other documents | STRING | N/A | 5/24/2022 | ||||
477 | Created Datetime | createdDatetime | The UTC timestamp for when the document was uploaded | TIMESTAMP_TZ | N/A | 5/24/2022 | ||||
478 | Loan Type | loanType | The specific product (Mortgage, HELOAN, HELOC, Auto, etc) | STRING | N/A | 5/24/2022 | ||||
479 | Title Provider Name | titleProviderName | Provider name associated with the title on the loan. e.g. Title365 | STRING | N/A | 5/24/2022 | ||||
480 | Title Property State | titlePropertyState | Abreviated state of the property on the title | STRING | N/A | 5/24/2022 | ||||
481 | ||||||||||
482 | ||||||||||
483 | ||||||||||
484 | ||||||||||
485 | ||||||||||
486 | Title Orders | |||||||||
487 | Reporting Dashboard Report: Title Orders | |||||||||
488 | Reporting API Endpoint: N/A | |||||||||
489 | This is a temporary table used for Blend Title Orders. It will not be added to the Reporting API in the foreseeable future. | |||||||||
490 | ||||||||||
491 | FIELD LONG NAME | FIELD NAME | DESCRIPTION | FIELD TYPE | API VERSION INTRODUCED | DATE INTRODUCED TO REPORTING DASHBOARD | ||||
492 | Loan Reference Number | loanNumber | The unique reference number associated with the loan | STRING | N/A | 5/24/2022 | ||||
493 | Loan ID | loanID | The UUID of the application in Blend's system. The static identifier that should be used to connect the application's identity across Blend and external integrations | STRING | N/A | 5/24/2022 | ||||
494 | Blend Order ID | blendOrderId | PRIMARY KEY - Unique ID of the activity | STRING | N/A | 5/24/2022 | ||||
495 | Loan Type | loanType | The specific product (Mortgage, HELOAN, HELOC, Auto, etc) | STRING | N/A | 5/24/2022 | ||||
496 | Order Date | orderDatetime | The UTC timestamp for when the order was created | TIMESTAMP_TZ | N/A | 5/24/2022 | ||||
497 | titleProviderName | appLeadSource | Specifies how an app was created (BORROWER, LENDER, INGEST, PUBLIC_API) | STRING | N/A | 5/24/2022 | ||||
498 | propertyState | userId | User ID for the user that completed the action (can be the user ID for a borrower or lender, or 'system') | STRING | N/A | 5/24/2022 | ||||
499 | propertyCounty | userType | The type for the user that completed the action. Can be system, borrower, or lender | STRING | N/A | 5/24/2022 | ||||
500 | ||||||||||
501 | ||||||||||
502 | ||||||||||
503 | ||||||||||
504 | ||||||||||
505 |
1 | User Guide | ||||||||
---|---|---|---|---|---|---|---|---|---|
2 | For Data Dictionary documentation | ||||||||
3 | |||||||||
4 | In this document you can find: 1) Data Dictionary - data dictionary for all fields available in Reporting Dashboard and the Reporting API 2) User Guide - a summary of available tables, and additional resource links at the bottom of this tab 3) Changelog - a changelog of what's been added since document creation. Please note: - The Data Dictionary only applies to the Reporting Dashboard in the lender portal and the Reporting endpoint in the API. To see what data is available for other endpoints in the API, please visit the API reference documentation. - For more information on accessing the Reporting Dashboard, visit the help center article on "Reporting In Blend: Overview" Please reach out to your Account Partner with any questions. | ||||||||
5 | |||||||||
6 | |||||||||
7 | |||||||||
8 | |||||||||
9 | |||||||||
10 | |||||||||
11 | |||||||||
12 | |||||||||
13 | |||||||||
14 | |||||||||
15 | |||||||||
16 | |||||||||
17 | |||||||||
18 | |||||||||
19 | |||||||||
20 | |||||||||
21 | Summary of Reports Available | ||||||||
22 | Reporting Dashboard Name | Reporting API Endpoint | Summary of Report | Date Introduced | |||||
23 | Data Verification Usage | Connectivity Metrics - /data-verification-usage | Provides a weekly view of aggregated metrics for data verification features such as asset connectivity, Blend Income, and The Work Number | 11/1/19 | |||||
24 | Application List | Basic Loan Data - /loans | A historical pipeline view of all loans in Blend including milestone metrics, application information (like application source), assignees, and different milestones and timestamps | 11/1/19 | |||||
25 | Borrower User List | Borrower Users - /borrowers | Provides a full list of borrowers and the current workflow they are on, invited and activated times, and timestamps for most recent credit, asset, and income pulls. | 11/1/19 | |||||
26 | PAB Activities | PAB Activities - /lender-pab-activities | Provides data on Lender Toolkit (previously "Pre Approval Builder") actions, including specific credit pull data and DU recommendations | 12/17/20 | |||||
27 | Lender User List | Lender Users and usage Metrics - /lenders | Provides a full list of lender users who have been invited or activated an account, as well as various usage metrics | 12/17/2020 | |||||
28 | Documents Meta | Documents Metadata - /documents | Provides a list of the type of documents uploaded on a loan (e.g. 1003, Bank Deposit Slip, 1099, HMDA Report, etc), and the User ID for who uploaded the document (e.g. Borrower User ID, or ‘system’ for automatically uploaded documents) | 11/1/19 | |||||
29 | Borrower Processes | Borrower Workflows - /activities | Provides data on borrower workflows. Can be used to derive a funnel for where borrowers drop off in application process | 11/1/19 | |||||
30 | NPS | NPS and Comments - /nps | Provides individual borrower NPS scores and comments | 11/1/19 | |||||
31 | Follow Ups | Follow-ups Data - /follow-ups | Provides a full list of individual follow-ups created on each loan along with the status. | 5/26/2020 | |||||
32 | Deposit Account Applications | Deposit Account Application Data - /deposit-account-applications | Deposit Account application data with information on the applications attributes and milestones. | 7/20/2021 | |||||
33 | Closings | N/A | Information on Blend Closings with timestamps. | 5/10/2022 | |||||
34 | Configurable Products - Applications | N/A | This table has one row per application for all products built on Blend's "Configurable Platform" | 2/8/2022 | |||||
35 | Configurable Products - Application Node History | N/A | This table has one row per node reached per application for all products built on Blend's "Configurable Platform". (A "node" is essentially a page or decisioning point or integration call defined in an application template by its developer, and a unique "node instance" is created when an individual application reaches each node in the workflow.) | 2/8/2022 | |||||
36 | Title Documents | N/A | A temporary report added as a subset of documents related to title, as well as associated title datt | 5/24/2022 | |||||
37 | Title Orders | N/A | A temporary report added containing information on individual title orders | 5/24/2022 | |||||
38 | |||||||||
39 | Resource Links | ||||||||
40 | API Reference | https://developers.blend.com/blend/reference | |||||||
41 | Reporting Dashboard | https://help.blend.com/hc/en-us/articles/360040529732-Reporting-in-Blend-Overview | |||||||
42 | v4.0.0 Changelog | https://developers.blend.com/blend/docs/v400-upgrade-guide | |||||||
43 | Previous Datadictionary | ||||||||
44 | |||||||||
45 | |||||||||
46 | |||||||||
47 |
1 | Changelog | |||||||
---|---|---|---|---|---|---|---|---|
2 | For Data Dictionary documentation | |||||||
3 | ||||||||
4 | ||||||||
5 | ||||||||
6 | DATE | TAB/TABLE | NOTES | |||||
7 | 12/1/20 | All | Document created | |||||
8 | 1/28/21 | Data Dictionary | 1. user_agent field added to Borrowers report 2. enums added to activity_type in Lender PAB Activities report 3. clarification added to uploaded_by_user_type in Documents report | |||||
9 | 8/31/21 | Data Dictionary | 1. Added Deposit Account Applications Report under 2. loan_number field added to PAB Activities, Borrowers, Borrower Processes, Followups, and NPS reports 3. los_milestone and los_milestone_last_updated_datetime added to Application List / Loans 4. Link added in the Documents table for all Document Types available https://info.blend.com/rs/287-UGB-469/images/BlendAPIDocTypes2.csv | |||||
10 | 11/20/21 | Data Dictionary | Deposit Accounts documentation added | |||||
11 | 1/15/22 | Data Dictionary | 1. Configurable Products - Applications report documentation added 2. Configurable Products - Application Node History report documentation added | |||||
12 | 2/22/22 | Data Dictionary | To Application List; /loans endpoint: 1. blendIncomeSuccessFlag - a boolean field indicating whether the loan had Blend Income Verification successfully run To Borrower User List; /borrowers endpoint: 2. incomeVerifiedDatetime - a timestamp (in UTC) of the latest Blend Income Verification for that borrower 3. lastUpdatedDatetime - a timestamp (in UTC) for the latest action on To Data Verification Usage; /data-verification-usage endpoint: 3.numberAssetsStatementFallback - the total number of Assets Statement (PDF) Fallback generated on any loan that had been submitted in that week 4. numberLoansWithAssetsStatementFallback - the number of submitted loans with at least one Asset Statement (PDF) Fallback generated within the week 5. percentSubmitsWithAssetsStatementFallback - the percent of submitted loans with at least one Asset Statement (PDF) Fallback generated in that week 6. numberAssetVerifiation - the total number of either Generated Asset Statements or Asset Statement (PDF) Fallback generated on any loan that had been submitted within the week 7. numberLoansWithAssetVerification - the number of submitted loans with either a Generated Asset Statements or an Asset Statement (PDF) Fallback generated within the week 8. percentSubmitsWithAssetVerification - the percent of submitted loans with at least one Asset Statement (PDF) Fallback or an Asset Statement (PDF) Fallback generated in that week 9. numberBlendIncomeVerifications - the total number of income verifications on any loan that had been submitted in that week 10. numberLoansWithBlendIncomeVerification - the number of submitted loans with at least one successful Blend Income Verification 11. percentSubmitsWithBlendIncomeVerification - the percent of submitted loans with at least one successful Blend Income Verification 12. Removed snake_case column for "Reporting Field Name" | |||||
13 | 7/1/22 | Data Dictionary | Configurable platform tables added | |||||
14 | 9/28/2022 | Document | 1. Data Dictionary document format updated 2. V4 transition tabs were removed (this document will reflect the most up to date version with columns indicating if the fields are in the API) 3. Columns added in every table for Field type, API Version introduced, and Date introducted to Reporting Dashboard. 4. Documentation added for new tables - Close, Title Orders, and Title Documents | |||||
15 | 03/21/23 | Data Dictionary | To Lender PAB Activities; /lender-pab-activities endpoint: 1. Added new row for ausProduct 2. Renamed duRecommendation field to ausRecommendation | |||||
16 | ||||||||
17 | ||||||||
18 | ||||||||
19 | ||||||||
20 | ||||||||
21 | ||||||||
22 | Resource Links | |||||||
23 | API Reference | https://developers.blend.com/blend/reference | ||||||
24 | Reporting Dashboard | https://help.blend.com/hc/en-us/articles/360040529732-Reporting-in-Blend-Overview | ||||||
25 | v4.0.0 Changelog | https://developers.blend.com/blend/docs/v400-upgrade-guide | ||||||
26 | Previous Data Dictionary | |||||||
27 | ||||||||
28 | ||||||||
29 | ||||||||
30 |