Clearer Validation Error Messages in the Home Lending - Applications API

Date Available: Beta 10/27, Prod 11/24

Which customers are impacted?: Lenders using the Home Lending - Applications API

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: This update improves error messages for loan updates submitted through Blend’s external Home Lending - Applications API. Previously, when a request failed validation, the API could return a generic error without identifying the field that caused the issue. This made it difficult for lender integration teams to troubleshoot and resolve sync failures.

With this update, error responses identify the specific field that failed validation and explain why it was rejected. This helps integration teams quickly identify and correct data issues, reducing troubleshooting time and improving visibility into loan sync failures.

Current Behavior: Some requests submitted through the external Home Lending - Applications API may return a generic “Invalid request” error when validation fails.

This can occur when a loan update is submitted with an incomplete property address. The error response does not identify the affected field or explain why the value was rejected, making it harder to diagnose and resolve the issue.

New Behavior: With this release, validation errors will identify the specific field that was rejected and explain the reason for the failure in the “error” field of the response. The “display” field is unchanged. A tracking ID will continue to be included for cases that require support assistance.

Validation behavior remains unchanged. The same requests will pass or fail validation as they do today; only the level of detail provided in error messages is changing.

No loan data will be modified as a result of this update, and no data repair is required.

Note: If your integration relies on an exact match to the existing “Invalid request” error message text, update that logic before this change takes effect to help maintain expected API error handling.

Known Limitations: Requests with empty or zero values may still be rejected. Consistent handling of empty values is planned for a future API version.

0 Votes