Last week I hosted the another "Check-In" which is our ten-minute monthly update on the latest in the Developer Platform. If you weren't able to join us, here's what's new:
1. Sales History Detail Call
The first update is a minor enhancement to the API. If you're not familiar, our sales history detail call shows 10 years of sales transaction history for any property. With the new update, the API now shows the sales history in order of most recent sale to oldest sale, by default. If you're looking to find the most recent sale, you won't have to worry about doing any sorting.
2. Area Hierarchy Call
The next update is to our Area Hierarchy Call. Previously, when you searched by a latitude and longitude, all of the boundaries that the point falls between would be returned. Now we've added a filter for geoType to allow you to be more efficient. If you’re only interested in zip codes or school boundaries, just add the geoType filter onto this call to make things a little faster and avoid having to search through all the results.
3. Search and Filter by Multiple Values
This next feature isn’t necessarily new, but I’ve gotten a lot of questions about it recently. Our API allows you to search and filter by multiple fields, for example, property type. If you're making a sales snapshot call, and you want to return all properties in a 5-mile radius from a current property and you only want to see single-family residences, and condos, you can filter by more than one property type at a time. That's through pipe delimited text which you can see in the sample call demonstrated in the video below. This works with any calls that aren’t a single value filter.
4. Updated Metrics Dashboard
We've also updated our metrics dashboard in the developer portal. The graph functionality has been expanded, so now you can view your usage from 24 hours, 7 days, 1 month, or even select specific days. You can see the total hits as well as the breakdown of how many calls were made and when they were made. This is a good way to make sure your hits are all successful and that you’re not making more calls than you need to.
5. Debug = True
I'd also like to point out our debug=true feature. Usually, if you have a null value return in a data field, that data field will not display in your API response. However, if you’re interested in seeing all the fields, regardless of if they are null, then add Debug=true to the end of your request. Again, please check out the video if you'd like to see a sample call. This is a good way to make sure when you’re building out your functionality, you’re taking into account all of these data fields, regardless of whether or not they're null.
6. Lookup Tables
The last feature that I wanted to point out is that we do offer lookup tables. If you’re not using the area hierarchy call or geo ID lookup call to pull back geo ID information, maybe you'd prefer to have a list of city names and how those relate to certain customers, we do offer lookup tables for our customers. This table is in CSV format, pipe delimited and allows your customers to search by city or neighborhood and it connects to the geo ID in our system so they can see points of interest or demographic data. This is a good way to avoid an additional API call, but still see geo ID data. If you're trying to implement your own auto-fill, this is a good way to set up your own based on a lookup table.
If you're interested in the full video and watching the sample calls in action, check out the full video below. Feel free to email questions to firstname.lastname@example.org.