ATTOM Data

1. Visit the ATTOM developer portal and sign in (or contact ATTOM Sales if you don't yet have an account — https://www.attomdata.com/contact/ is the entry point).
2. Once logged in, your API key is shown on the My Account / Subscriptions page.
3. Copy the key value — it's a single opaque string that ATTOM authenticates via the apikey header (lowercase, verbatim).

In the Ingest UI under Connectors → ATTOM Data, paste the key. Ingest stores it in AWS Secrets Manager under the key apikey.

ATTOM does not publish a per-second rate cap, so the Ingest runtime defaults to a conservative 2 req/sec with AIMD backoff on 429 responses. Errors with status 400 (no results — treated as an empty payload, not a failure), 401 (bad key), 403 (out-of-scope endpoint for your subscription), or 404 (no record found) are handled inline.

The response envelope is:

{ "status": { "code": 0, "msg": "SuccessWithResult", "total": 1, "page": 1, "pagesize": 10 },
  "property": [ { ... } ] }

status.code == 0 means success with results; status.code == 400 means success with zero results (the connector treats this as an empty array, not an error).

ATTOM endpoints fall into two groups:

• Seed — property_id resolves an address to ATTOM's internal attomId. This is the gateway endpoint; almost every other endpoint expects an attomId. salestrend is the one independent endpoint, providing zip-level market trends.
• Per-property (joined to property_id) — property_expandedprofile, sale_detail, saleshistory_expanded, assessment_detail, assessmenthistory, avm_detail, avmhistory, rental_avm, allevents, school_search. Enable the ones your use case needs; each is orthogonal.

For most customers the property_expandedprofile + sale_detail + assessment_detail triad covers the canonical "property snapshot" use case. AVM endpoints are for valuation work; the schools endpoint is for housing/relocation tools.