Expose Borrower SMS Consent in MISMO and APIs

Date Available: Beta 2/17, Prod 3/10

Which customers are impacted?: Lenders who have borrower SMS enabled.

Required? Yes, this is a required release. Required releases are features that Blend wants to standardize in the codebase, and typically do not require additional configuration. 

How to turn on: This feature will be automatically enabled on the dates listed above.

Purpose of Update and Benefit: Blend’s partners and customers want visibility into whether a borrower has provided SMS consent. This update exposes borrower SMS consent information via the MISMO and Public APIs, enabling LOS systems and downstream workflows to consume and export this data.

Current Behavior: Borrower SMS consent was only captured within Blend and was not accessible externally.

New Behavior: Borrower SMS consent is now exposed through the MISMO and Public APIs, allowing external systems to retrieve and use this information.

MISMO Field Names

• SmsConsentStatusIndicator

• SmsConsentStatusText

• SmsConsentPhoneNumber

• SmsConsentPauseStatusIndicator

Public APIs v11.0.0

The following endpoints now include SMS consent data:

• GET /home-lending/applications

• GET /home-lending/applications/:id

• GET /home-lending/applications/:id/parties

A new “smsConsent” object is added to the API response with the following fields:

• “status”: enum values PENDING, ACCEPTED, DECLINED

• “recipientPhoneNumber”: phone number for SMS notifications

• “paused”: whether SMS notifications are paused

• “date”: UTC timestamp of when consent was given by user

• “ip”: IP Address from which consent was given

The “smsConsent” object is included in the response if the user has been presented with the SMS consent flow.

0 Votes