API Endpoints Overview

Last updated: January 12, 2026

This article explains how to make requests to the ATTOM API and understand the structure of an API call, using real-world examples.

At a high level, querying the ATTOM API means:

  1. Choosing the endpoint that returns the data you need

  2. Supplying search criteria (such as an address, APN, or location)

  3. Sending the request and receiving structured property data in response

Making an API Request

Every ATTOM API request follows the same basic structure:

Base URL + API version + endpoint + search parameters

You don’t need to memorize this structure—most of the time, you’ll start with an example and adjust the search parameters to fit your use case.

Example Requests

Below are a few common examples to show how different endpoints are used.

Look up a property by address

This request uses the Basic Profile endpoint to return core property details for a specific address.

https://api.gateway.attomdata.com/propertyapi/v1.0.0/property/basicprofile?address=4529 Winona Court, Denver, CO

Look up a property by APN and county

This request searches for a property using an APN, along with a county FIPS code.

https://api.gateway.attomdata.com/propertyapi/v1.0.0/property/basicprofile?apn=02192-04-018-000&fips=08031

Find properties near a location

This request uses the Address endpoint to return all properties within a 0.5-mile radius of a latitude/longitude coordinate.

https://api.gateway.attomdata.com/propertyapi/v1.0.0/address?latitude=39.21523130910493&longitude=-75.62095642089844&radius=0.5

Filter and sort properties by AVM

This request uses the AVM Detail endpoint to find properties in a specific ZIP code that meet certain criteria, then sorts results from highest to lowest AVM value.

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

Retrieve community-level information

This request returns community data for a specific place using a geoidv4, which is typically obtained from a prior property lookup.

https://api.gateway.attomdata.com/v4/neighborhood/community?geoidv4=76e288aaf6820a1206681d40d9ee96ef

API Environments

ATTOM provides multiple environments so you can test your integration safely before going live.

Production

Use this environment for live applications and real data usage:

https://api.gateway.attomdata.com/

Sandbox

A Sandbox environment is available for testing. Access must be requested separately.

API Versions

ATTOM APIs evolve over time as new data is added and improvements are made. Most enhancements do not require changes to your existing code.

Occasionally, a change is introduced that is not backward-compatible. When this happens, ATTOM releases a new API version. Older versions may eventually be deprecated, at which point you’ll need to update your integration.

Older versioning format

Earlier APIs used component-based naming and semantic versioning, such as:

  • propertyapi/v1.0.0

  • communityapi/v2.0.0

  • areaapi/v2.0.0

Current versioning (v4 and newer)

Starting with version 4, ATTOM simplified the structure by:

  • Removing component-based API names

  • Using a single version number (for example, v4)

This makes endpoints easier to read, easier to maintain, and more consistent across products.