We use cookies to try and give you a better experience in Freshdesk.
You can learn more about what kind of cookies we use, why, and how from our Privacy policy. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies.
We’ll also assume you agree to the way we use cookies and are ok with it as described in our Privacy policy, unless you choose to disable them altogether through your browser.
Date Available: Beta 3/27, Prod 5/5
Which customers are impacted?: Any lender planning to upgrade to Blend API v12.
Required?: No, opt-in.
How to turn on: API v12 is currently available in beta for testing. On 5/5/2026, v12 will be promoted to stable status and made available for production use.
Purpose of Update and Benefit: This release introduces enhancements to the Home Lending and Follow-Ups APIs to support improved loan grouping, consent tracking, and enriched follow-up context. These updates provide greater flexibility for integrations while improving visibility into loan assignment, borrower consent, and follow-up metadata. All changes are non-breaking and optional.
Home Lending API Updates:
Introduced an optional groupId field (UUID) to support assigning loans to a group. This field is available in application creation and update endpoints, and is also returned in application responses when present. Invalid values will return a 400 Bad Request.
Added a consentToLenderContactGiven object in application and party responses, providing consent status (PENDING, ACCEPTED, DECLINED), along with the timestamp and IP address of consent.
Follow-Ups API Updates:
W-2 follow-ups now support optional employer context, including employerId and employerName, to improve data enrichment for employer-related workflows.
When provided, these fields are persisted and returned in follow-up responses.
Added an optional paymentTransactionId field in follow-up responses to include the payment gateway transaction ID for successful upfront fee payments, when applicable.
Current Behavior: API v12 is currently in beta and available for testing.
New Behavior: On 5/5/2026, API v12 will be updated from beta to stable status and made available for production use. The full set of changes included in this release can be reviewed in the v12 changelog.
0 Votes
0 Comments
Login to post a comment