api.developer.attomdata.com APIapi.developer.attomdata.com ↗
Access ATTOM property details, owner records, neighborhood POI, and sales trend data via 5 structured endpoints covering addresses, geographies, and more.
curl -X GET 'https://api.parse.bot/scraper/7d4d00ce-c23d-4935-a089-995a4e9497d6/get_property_address?page=1&pagesize=2&postalcode=90210' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns properties within a specified area or matching address criteria.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number |
| radius | number | Search radius in miles |
| address1 | string | Street address line 1 |
| address2 | string | City, state, zip |
| latitude | number | Latitude for radius search |
| pagesize | integer | Results per page |
| longitude | number | Longitude for radius search |
| postalcode | string | Postal/ZIP code to search |
| propertytype | string | Property type filter |
{
"type": "object",
"fields": {
"status": "object",
"property": "array"
},
"sample": {
"data": {
"status": {
"msg": "SuccessWithResult",
"code": 0,
"page": 1,
"total": 9429,
"version": "1.0.0",
"pagesize": 2,
"transactionID": "f4bf202a669467a2d0cdb7760cc83e59",
"responseDateTime": "2026-02-26T00:22:43.312Z"
},
"property": [
{
"address": {
"line1": "502 N ALTA DR",
"line2": "BEVERLY HILLS, CA 90210",
"country": "US",
"oneLine": "502 N ALTA DR, BEVERLY HILLS, CA 90210",
"postal1": "90210",
"postal2": "3502",
"postal3": "C011",
"locality": "BEVERLY HILLS",
"matchCode": "ExaStr",
"countrySubd": "CA"
},
"vintage": {
"pubDate": "2025-10-14",
"lastModified": "2025-10-14"
},
"location": {
"geoid": "CO06037, CS0691750, ND0004780424, PL0606308, SB0000068678, SB0000068680, ZI90210",
"geoIdV4": {
"CO": "c901b0c78f08f2e777cce3d16936fd0e",
"CS": "c5d84093eb167032a75ea743fd5f2f81",
"DB": "938838cffdba658277c328179d6d9166",
"N1": "ba85655100a0573f28372da416303c28",
"PL": "759869c1bf6d2bca73c7291f9a7959f0",
"SB": "455e6b356ca9102619ffa1aa7dbbcae8, 3b1c5e204f0c6fd74e749b74c2449b0c",
"ZI": "ecf7b806ad7dea1def2c60b246364d06"
},
"accuracy": "Rooftop",
"distance": 0,
"latitude": "34.079958",
"longitude": "-118.392471"
},
"identifier": {
"Id": 111904,
"apn": "4341-003-001",
"fips": "06037",
"attomId": 111904
}
},
{
"address": {
"line1": "511 N BEDFORD DR",
"line2": "BEVERLY HILLS, CA 90210",
"country": "US",
"oneLine": "511 N BEDFORD DR, BEVERLY HILLS, CA 90210",
"postal1": "90210",
"postal2": "3213",
"postal3": "C026",
"locality": "BEVERLY HILLS",
"matchCode": "ExaStr",
"countrySubd": "CA"
},
"vintage": {
"pubDate": "2025-10-14",
"lastModified": "2025-10-14"
},
"location": {
"geoid": "CO06037, CS0691750, DB0604830, ND0004780424, PL0606308, ZI90210",
"geoIdV4": {
"CO": "c901b0c78f08f2e777cce3d16936fd0e",
"CS": "c5d84093eb167032a75ea743fd5f2f81",
"DB": "938838cffdba658277c328179d6d9166",
"N1": "ba85655100a0573f28372da416303c28",
"PL": "759869c1bf6d2bca73c7291f9a7959f0",
"SB": "518dd0b4740f4cc4327409bfa11c3ddb, 3b1c5e204f0c6fd74e749b74c2449b0c",
"ZI": "ecf7b806ad7dea1def2c60b246364d06"
},
"accuracy": "Rooftop",
"distance": 0,
"latitude": "34.070421",
"longitude": "-118.408060"
},
"identifier": {
"Id": 156593,
"apn": "4345-028-003",
"fips": "06037",
"attomId": 156593
}
}
]
},
"status": "success"
}
}About the api.developer.attomdata.com API
The ATTOM Data API exposes 5 endpoints covering property search, detailed property attributes, owner records, neighborhood points of interest, and geographic sales trends. get_property_detail_owner returns current ownership data alongside full property records, while get_transaction_sales_trend aggregates yearly or monthly transaction metrics for a given geography — useful for market analysis pipelines that need structured, address-level real estate data.
Property Search and Detail
get_property_address accepts street address components (address1, address2), a postal code, or a latitude/longitude pair with an optional radius (in miles) to return a paginated property array matching those criteria. get_property_detail narrows to a single property using either an attomid or a full address, returning a rich property array with detailed attribute fields. get_property_detail_owner requires an attomid and adds current owner information to that same structure — ownership data is only accessible through this dedicated endpoint, not through the general detail call.
Sales Trends by Geography
get_transaction_sales_trend returns a salesTrends array for a target geography defined by a geoidv4 — a 32-character hex identifier available in the geoIdV4 field of property responses. Required inputs are startyear, endyear, and geoidv4. The interval parameter accepts 'yearly' or 'monthly'. Geography type is encoded in the ID prefix: ZI for ZIP code, CO for county, PL for place, CS for census tract, and DB for district. An optional propertytype filter narrows results to a specific asset class.
Points of Interest
get_poi_search returns a poi array for locations near an address, ZIP code, or a WKT-style point string formatted as POINT(longitude,latitude). A categoryid parameter filters by POI type. The recordlimit parameter caps results (default 20), and standard page/pagesize parameters control pagination across larger result sets.
- Enriching property listings with ownership records pulled from
get_property_detail_owner - Building neighborhood scorecards by querying nearby amenities via
get_poi_searchwithcategoryidfilters - Generating market trend dashboards using
get_transaction_sales_trendwith monthly interval data over multi-year ranges - Geocoding-free property lookups by passing
address1andaddress2toget_property_detail - Radius-based property prospecting by supplying latitude, longitude, and a mile radius to
get_property_address - Comparing sales velocity across ZIP codes and counties by switching
geoidv4prefixes in trend queries - Populating CRM records with structured property attributes from the
propertyresponse array
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does ATTOM Data have an official developer API?+
How do I obtain the `geoidv4` value needed for sales trend queries?+
get_transaction_sales_trend requires a geoidv4 that comes from the geoIdV4 field returned in property responses — for example, from get_property_detail. The prefix of the 32-character hex hash encodes geography type: ZI for ZIP code, CO for county, PL for place, CS for census, and DB for district. There is no dedicated endpoint to look up geography IDs independently.Does the API return historical ownership or mortgage/lien data?+
get_property_detail_owner. Historical ownership chains, mortgage records, and lien data are not exposed by these endpoints. You can fork this API on Parse and revise it to add endpoints that cover those additional ATTOM data products.What is the difference between `get_property_detail` and `get_property_detail_owner`?+
get_property_detail accepts either an attomid or an address pair and returns property attribute data. get_property_detail_owner requires an attomid and returns that same property structure augmented with current owner information. Owner fields are not present in the base detail response.