What's New - May 2023

New Features

The ATTOM Cloud team has been hard at work improving the product. This month we are pleased to announce the following new features have been added

New Introductory Video

After two years of releasing new features and enhancements to ATTOM CLoud, we are pleased to announce that we have recorded a new Introductory Video for ATTOM Cloud that demonstrates many of these new features. The video can be found in the Learn section of the ATTOM Cloud home page.

Quality of Life

The feedback you provide helps us identify the ways in which ATTOM Cloud can be tweaked to make your experience with the product a better one.

Registration/Login Logging

To help us to help you, we have added additional logging of ATTOM Cloud sessions to keep track of problems encountered during the registration and sign-in processes. Whenever a problem is reported, we can then verify the exact steps followed, making it easier for us to diagnose and correct any issues you may be having.

APN Search

We have investigated an issue searching for properties via Assessor Parcel Numbers (APNs) when using ATTOM API endpoints such as Expanded Profile. Searches previously taking as long as 1.5 minutes are now taking less than 1500 ms.

Identifying Invalid Parameters

Calls made to ATTOM API that pass a parameter that is not recognized or no longer supported would respond with a generic 400 Bad Request error. We have enhanced the message returned to better identify the cause of the problem. The error message returned now reads "Invalid parameter(s) in request - xxx" where xxx is the name of the parameter that is not recognized by the endpoint called.

Bugs

Sometimes in a rush to deliver new features and enhancements, we allow bugs to creep into the code. We're pretty sure there are a lot more that haven't yet been found, but of those that have been discovered by our customers or the team here at ATTOM, the following are some that we believe we have squashed this month.

Addresses with Comas

Users of our DLP API reported issues when searching for addresses in which the street address used for the search contained commas. We have identified the cause of the problem and made a correction.

Foreclosure Recording Date

API Endpoints such as Expanded History that return the Recording Date of Foreclosures were found to be returning the wrong dates. Instead of returning the date on which the foreclosure was recorded, we were returning the date the record was last updated. We have fixed this issue. We thank those of you who pointed this out to us.