How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ATTOM Lookup API

Lookup of state, county, CBSA, and geoID metadata.

ATTOM Lookup API is one of 18 APIs that ATTOM publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include Lookup. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 6 JSON Schemas.

This API exposes 6 operations across 6 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version v1.0.0.

Requests are made against a single base URL, https://api.gateway.attomdata.com.

6 operations 6 paths 3 schemas 6 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1.0.0
Base URL
https://api.gateway.attomdata.com/propertyapi/v1.0.0
Authentication
API Key
Resource Areas
1

Authentication & Security 1

ATTOM Lookup API declares 1 security scheme for authenticating requests. An API key is passed in the header as apikey (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — ATTOM-issued API key. Pass on every request via the apikey header.

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 6 GET. Each is listed below with its method, path, parameters, and response codes.

Lookup 6

Lookup of state, county, CBSA, and geoID metadata.

GET
/areaapi/area/state/lookup
Lookup State
getStateLookup 2 params → 200
GET
/areaapi/area/county/lookup
Lookup Counties By State
getCountyLookup 1 param → 200
GET
/areaapi/area/cbsa/lookup
Lookup CBSAs
getCbsaLookup 1 param → 200
GET
/areaapi/area/geoid/lookup
Lookup By GeoID
getGeoIdLookup 4 params → 200
GET
/areaapi/area/geoId/legacyLookup
Lookup Legacy GeoCode
getGeoCodeLegacyLookup 1 param → 200
GET
/v4/location/lookup
Lookup Location By GeoIdV4
getLocationLookupV4 2 params → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Area (7 properties), Status (4 properties), AreaEnvelope (2 properties). Each schema is shown below with its type and property counts.

Area
object
7 properties
AreaEnvelope
object
2 properties
Status
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

attomdata-lookup-api-openapi.yml Raw ↑

Other APIs ATTOM publishes across the network.

ATTOM All Events API
ATTOM Assessment API
ATTOM AVM API
ATTOM Boundary API
ATTOM Building Permits API
ATTOM Community API
ATTOM Hierarchy API
ATTOM Home Equity API
ATTOM Location API
ATTOM Parcel Tiles API
ATTOM POI Categories API
ATTOM POI Search API
Where this information came from

This is an independent, third-party profile of ATTOM Lookup API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.