ATTOM API Endpoints
ATTOM API URI
Each ATTOM API endpoint has its own Uniform Resource Identifier (URI). These URIs follow the following pattern
{API-URL}/{API-Version}/{Endpoint}/{Route}?{query}
Examples
The following example calls the Basic Profile endpoint to search for a property with a specific address
https://api.gateway.attomdata.com/propertyapi/v1.0.0/property/basicprofile?address=4529 Winona Court, Denver, CO
The following example calls the Basic Profile endpoint to search for a property in a specific county with a specific APN
https://api.gateway.attomdata.com/propertyapi/v1.0.0/property/basicprofile?apn=02192-04-018-000&fips=08031
The following example calls the Address endpoint, conducting a radius search that returns all properties located in a 0.5-mile radius of a specific coordinate (latitude/longitude)
https://api.gateway.attomdata.com/propertyapi/v1.0.0/address?latitude=39.21523130910493&longitude=-75.62095642089844&radius=0.5
The following example calls the AVM Detail endpoint to return all properties in a specific zip code matching certain characteristics, where the AVM falls within a specified range and returns the results sorted from highest AVM to lowest AVM
https://api.gateway.attomdata.com/propertyapi/v1.0.0/attomavm/detail?maxavmvalue=2500000&maxbeds=6&minavmvalue=1000000&minbeds=4&minuniversalsize=3000&minyearbuilt=2015&postalcode=92620&propertyindicator=10&orderby=avmvalue+desc
The following example calls the Community endpoint to return community information for the Place of "Morton, Delaware County, PA". The value of geoidv4 may have been found as the result of doing a previous property lookup.
https://api.gateway.attomdata.com/v4/neighborhood/community?geoidv4=76e288aaf6820a1206681d40d9ee96ef
API-URL
ATTOM API has assigned different URLs for each environment. Currently, ATTOM API supports a Production environment and a Sandbox environment that can be used for testing the API. Note: A separate request needs to be made to access the Sandbox environment.
Production: https://api.gateway.attomdata.com/
API-Version
ATTOM Cloud and ATTOM API should be considered as being dynamic products. We are constantly striving to put the latest property data in the hands of our users with weekly releases. Because of this, we often add new data to existing API endpoints. This should not impact existing code. Occasionally, we have to make what is called a "breaking change" - a change that might break existing code. To allow us to continue to enhance ATTOM API, we release these changes as a new "version" of the endpoint. Customers will need to change any existing code to use the new version. After a while, old versions may get deprecated, requiring customers to modify and test the newest version of the endpoint.
As ATTOM API has evolved we have adopted different naming standards for our endpoints, breaking the product into component APIs.
- areaapi/v2.0.0
- communityapi/v2.0.0
- propertyapi/v1.0.0
Starting with version 4 of ATTOM API, we have simplified this by dropping the component api and reducing the version number from a major.minor.point number scheme (e.g. 1.0.0) to a simple version number (e.g. v4).