Attom Data API

Created by Sydney Bocik · February 16, 2026 · Last updated March 16, 2026 · Category: API & Integrations

API and coverage information available at: https://nexus.attomdata.com/

(Previously under docitt email but made a new nexus account under purlend email)

Pricing

ATTOM API pricing is based on the number of calls per month. It is an annual subscription, paid monthly.

Q&A with ATTOM

How does ATTOM define a single "API call" for billing purposes?

Every endpoint called is a single call.

If a single user workflow requires pulling data from multiple ATTOM APIs (for example, property details + valuation + tax), would each endpoint request count as a separate call?

Yes.

Do you ever work with clients to consolidate or batch data across endpoints into a custom or bundled API to reduce call volume for a single use case?

We do have customers who cache the data.

What are your policies around temporarily storing response data (e.g., caching during a user session) to complete a workflow, assuming the data is not stored long-term or resold?

Yes, as noted above until the contract ends.

Minimum commitments and fluidity in tiers based on consumption for billing? And rollover amounts based on minimum commitments?

It is very easy to move up in tiers throughout the contract year. You need to call your Account manager to do amendment.

The call credits do not roll over. You are charged the tier pricing of choice each month. Overages billed @.20

Our ATTOM API pricing is based on the number of calls per month. It is an annual subscription, paid monthly.

Building Permit Data is an additional $100/month.

For overage pricing, I noticed the starting tier equates to about $0.15 per API call, while overages are billed at $0.20 per call. I would have expected the worst-case pricing to align with the starting tier rate. Can you help me understand the rationale for overages being priced higher?

Incentive to move up a tier.

For tier change timing and flexibility, I understand moving up tiers requires a manual request. When we submit a request, does the new tier take effect within the same billing month, or is there typically a lag? If there is a lag, should we expect it to take effect the following month, or longer? Also, if we move up a tier and our usage later decreases, can we move back down tiers as easily, or are there restrictions once a higher tier is selected?

The request will be done and noticed in the next billing period. After the 1yr contract, you can move down a tier.

For platform integration and partner usage, we will be building products that integrate ATTOM data as part of a broader property insights layer. We are not reselling ATTOM data directly, but multiple companies will be using our platform, which includes ATTOM-powered insights.

OK.

For tier overages within a billing cycle, let's say we hit our tier limit for one month but weren't expecting to. Will the API block the overage, or will it allow the calls to go through, and we'd just be billed for it? We just want to make sure that there are no interruptions to the service for the end users.

Your service will never be interrupted due to API overages.

Are there any restrictions or licensing considerations for this type of usage that you can share now, so we can ensure we are fully aligned and structured appropriately from the beginning?

You can see our on Contract draft.