History of ATTOM API

The first version of ATTOM's property API is known as DLP. It is no longer being sold as a product, but it continues to be maintained for those customers who haven't yet migrated to ATTOM API.

DLP Version 1

The original version of ATTOM's API product is now known as DLP version 1. The data was sourced from the original RealtyTrac database established before the company was renamed to ATTOM. DLP followed the MISSMO specification. The latest published version was 1.18.0.

  • Property API

DLP Version 1 remains the only source of PlatMaps. All other endpoints have been deprecated and/or migrated to ATTOM API.

DLP Version 2

New Azure SQL Server databases were developed specifically for supporting a cloud-based property API. 3SCale was adopted as the API management platform. The API was expanded to include Neighborhood (community) data available from OBI such as air quality, demographics, natural hazards, poi, and schools.

  • Neighborhood API (deprecated)
  • Property API

Documentation: https://api.developer.attomdata.com/dlpv2docs

DLP Version 3

A new preforeclosure endpoint was added for existing DLP customers. The MISSMO payload was replaced with a new standard based on ATTOM's new cloud platform that was being adopted by the ATTOM API. This endpoint was later migrated to ATTOM API Versions 3.0.0.

  • Neighborhood API (deprecated)
  • Property API (new endpoint now deprecated)

ATTOM API is ATTOM's strategic Property API offering.

ATTOM API Version 1.0.0

Following the acquisition of Onboard Informatics (OBI) in 2018, a new API was developed with a collection of property-centric endpoints. This API combined ideas from DLP and OBI's own API using its own payload structure in place of the MISSMO specification used in DLP. ATTOM API was offered as an alternative to the existing DLP API.

  • Property API

ATTOM API Version 2.0.0

ATTOM API was extended beyond property-centric endpoints with three additional component APIs (Area, Community, and POI). The Property API was extended with the addition of a Sales Comparables endpoint.

  • Area API
  • Community API
  • POI API
  • Property API (new endpoint)

ATTOM API Version 3.0.0

The preforeclosure endpoint was migrated from DLP version 3, making it available to ATTOM API customers. It was decided to retain the version numbering used by DLP.

  • Property API (new endpoint)

ATTOM API Version V4 (Current)

In 2022, ATTOM began the work of replacing the OBI database that had been used to support earlier versions of ATTOM API. With Version 4, endpoints using Area, Community, POI, and School data sourced data from ATTOM Cloud. ATTOM Cloud was extended to include Elastic, allowing boundary files to be supported. To simplify the upgrade, it was decided to move all affected endpoints to V4. Older endpoints using data from the OBI database were deprecated on June 30, 2023.

  • Area API
  • Community API
  • POI API
  • Property API (select endpoints)

The component APIs (have been dropped from the URI and the version numbers have been simplified to a single number e.g. V4 instead of propertyapi/4.0.0.

See ATTOM API V4 for further details.

Documentation: https://cloud-help.attomdata.com/article/527-using-attom-api

Other APIs

Estated

ATTOM acquired Estated in 2022. ATTOM continues to support the Estated API, but it does not currently market this to new customers. Work is currently underway to reproduce the functionality of the Estated API within ATTOM API, providing a migration path for customers wanting to combine the features they like about Estated Essentials and Estated Enhanced with the broader capabilities of ATTOM API.

Documentation: https://estated.com/developers/docs/v4

Geo Data Plus

ATTOM acquired Geo Data Plus in 2021. This has formed the basis for the Property Navigator product. Like ATTOM API, Property Navigator also sources its data from ATTOM Cloud. An API developed as part of Geo Data Plus is no longer been actively marketed. Work is underway to reproduce the functionality of the Geo Data Plus API within ATTOM API, providing further options for customers wanting to use our API to drive content for property portals.

Slipstream

ATTOM acquired Home Junction in 2020. Home Junction's API product is called Slipstream and provides a combination of property, area, and MLS endpoints. ATTOM continues to sell its Slipstream MLS API to customers that meet the use cases permitted to license MLS data under BBO, IDX, or VOW licenses. Work is underway to reproduce the functionality of Slipstream's property endpoints, providing a migration path for customers wanting to combine the features found in Slipstream Property API with the broader capabilities of ATTOM API.

Note: There are no plans at this time to incorporate Slipstream MLS endpoints into ATTOM API.

Documentation: https://slipstream.homejunction.com/#/?id=introduction

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Related Articles