RealtyCrawl
US Address Property Composite platformUS Address Property Composite API

Fetch US Address Property Composite data with one API

Resolve a US street address through a composite of pinned Apify sources: county assessor records (published owner of record, tax-roll values, characteristics), recorder deed/mortgage/lien index documents, and a Zillow portal detail page (specs, photos, Zestimate). Owner is the assessor owner of record, not verified title; recorded documents are index evidence, not a lien search; values are not appraisals. Documentation-backed beta.

Read the docs How it worksTry a request

What US Address Property Composite endpoints does RealtyCrawl ship?

Resolve a US street address through the pinned county-assessor, recorder-index and portal composite, then read the retained prop_usproperty_ observation. Per-source outcomes and explicit gaps are preserved. Each endpoint has a documented request, response schema, and credit cost.

Resolve a US address property

50 credits

POST /v1/properties/resolve

Resolve a US street address through the assessor, recorder and portal composite.

address

Read a saved property observation

1 credits

GET /v1/properties/{property_id}

Read your account’s saved address-composite property observation.

property_id

Read a saved portal listing

1 credits

GET /v1/properties/{property_id}/listings

Read the portal advertisement saved with your address-composite property, when one was observed.

property_id

Read saved property records

1 credits

GET /v1/properties/{property_id}/records

Read assessor, recorder-index and portal records saved with your address-composite property.

property_id

Read a saved assessor sale

1 credits

GET /v1/properties/{property_id}/transactions

Read the assessor-reported sale saved with your address-composite property, where published.

property_id

Read a saved assessor snapshot

1 credits

GET /v1/properties/{property_id}/tax-assessments

Read the county assessor valuation snapshot saved with your address-composite property.

property_id

Read tax-roll and portal-model estimates

1 credits

GET /v1/properties/{property_id}/valuations

Read tax-roll and portal-model estimates saved with your address-composite property; not appraisals.

property_id

Check live capabilities for operation and market availability. Unavailable requests are not charged.

Checking current source coverage…

Source request · Fetches the source through the enabled adapter.

US Address Property Composite API
7 endpoints documented
View docs
POST/v1/properties/resolveGet API key
curl -X POST 'https://realtycrawl.dev/v1/properties/resolve' \
  -H "x-api-key: $REALTYCRAWL_API_KEY" \
  -H 'X-Max-Credits: 50' \
  -H "Idempotency-Key: YOUR_IDEMPOTENCY_KEY" \
  -H "content-type: application/json" \
  -d '{"address":{"formatted":"123 Example Street, Austin, TX","country":"US"}}'
API key required
// Live requests require a RealtyCrawl API key.
// Copy the request to your backend and set REALTYCRAWL_API_KEY.
// Check source and operation availability before running a request.

How the US Address Property Composite API works

Integrate a source-linked real estate API with standard HTTP requests, one API key, and structured JSON responses.

Authenticate every call

Send your RealtyCrawl API key in the x-api-key header. Keep it in your server environment.

GET and POST requests

Use path and query parameters for GET requests. Send a JSON body for POST operations.

One credit system

Source requests cost 50 credits per successful call. Saved reads cost 1 credit per observation, including successful saved-batch items. Failed calls are refunded; usage and balance appear in the response headers.

JSON and data exports

JSON keeps data and meta together. Field projection and CSV/NDJSON exports are response options; export request and credit metadata stays in headers.

The usual integration chain

From a supported source operation to data in your application.

  1. 1CheckGET /v1/meta/capabilitiesConfirm coverage and accepted selectors.
  2. 2RequestPOST /v1/properties/resolveSend the inputs for the selected operation.
  3. 3Readdata + metaInspect results, source outcomes, and warnings.
  4. 4ConnectYour applicationPreserve identifiers and observation times.

Request

curl --request POST 'https://realtycrawl.dev/v1/properties/resolve' \
  --header "x-api-key: $REALTYCRAWL_API_KEY" \
  --header 'X-Max-Credits: 50' \
  --header 'Content-Type: application/json' \
  --header 'Idempotency-Key: YOUR_IDEMPOTENCY_KEY' \
  --data '{"address":{"formatted":"123 Example Street, Austin, TX","country":"US"}}'

Illustrative response

{
  "data": {"status":"matched","candidates":[{"id":"prop_usproperty_4b825dc642cb6eb9a060e54bf8d69288","entity_type":"property","confidence":null,"method":"exact_source_us_property_address","source":{"platform":"us_property","native_id":"29419686","provider":"example","observed_at":"2026-01-01T12:00:00Z","access_class":"public_portal"}}]},
  "meta": {
    "request_id": "example_request",
    "schema_version": "1.0.0",
    "generated_at": "2026-01-01T12:00:00Z",
    "completeness": "partial",
    "sources": [
      {
        "platform": "us_property",
        "status": "partial"
      }
    ]
  }
}

What lands in data

Source context stays with the property observations.

Property
address · property_type · bedrooms · areas
Records
property_record · tax_assessment · recorded_document
Estimates
tax-roll market · portal model
Source
platform · provider · observed_at · access_class

Inside the gateway

One request keeps the source, operation, and result connected.

01

Operation selection

Your path selects the platform and operation. Capabilities describe accepted selectors and markets.

02

Source collection

The gateway routes supported requests to the configured source and records its outcome.

03

Contract normalization

Property attributes, prices, and units are mapped into a shared JSON schema.

04

Response metadata

Completeness, warnings, and source timestamps help your application interpret the result.

Billing rules that make evaluation clear

  • Source requests cost 50 credits per successful call. Saved reads cost 1 credit per observation, including successful saved-batch items.
  • 500 signup trial credits
  • Failed calls are refunded
  • Usage in response headers
  • Set an X-Max-Credits budget
  • One key across the catalog

How we get the data

A source request becomes a structured observation, with its origin and collection time attached.

What your request targets

US Address Property Composite street-address property composite records through a supported listing operation. Catalog markets: United States.

How records are returned

Search returns normalized listing IDs for saved reads. Use URL or native-ID detail only where that source operation is documented and enabled.

What comes with each result

Operation-specific resource fields sit alongside source identifiers, collection times, and completeness metadata.

What an observation means

Collection time and source update time describe different events. Stored observations expire after 24 hours without triggering a fresh crawl.

SOURCE → SHARED SCHEMA

Listing identifier

→ source.native_id

Published asking price

→ price.amount + currency

Collection timestamp

→ source.observed_at

What this API
is used for

Source-linked data for property products and research.

7

documented operations

1–50

credits per call / batch item

property workflows

Resolve a US street address through the pinned county-assessor, recorder-index and portal composite, then read the retained prop_usproperty_ observation. Per-source outcomes and explicit gaps are preserved.

Coverage and field availability vary by source. Check capabilities before you start a workload.

What people build with the US Address Property Composite API

Turn street-address property composite observations into tools your team can use.

Use case examples

Connect one source to the tools and workflows you already use.

Search applications

REST · application backend

Search returns normalized listing IDs for saved reads. Use URL or native-ID detail only where that source operation is documented and enabled.

Research pipelines

JSON · notebooks · BI

Compare property observations with their currencies, area units, and timestamps.

Assistant workflows

MCP · tools · agents

Give an assistant supported data operations with explicit request budgets.

Make your first request

Choose an operation, supply its inputs, and send your API key from your backend.

Resolve a US address property

curl --request POST 'https://realtycrawl.dev/v1/properties/resolve' \
  --header "x-api-key: $REALTYCRAWL_API_KEY" \
  --header 'X-Max-Credits: 50' \
  --header 'Content-Type: application/json' \
  --header 'Idempotency-Key: YOUR_IDEMPOTENCY_KEY' \
  --data '{"address":{"formatted":"123 Example Street, Austin, TX","country":"US"}}'

Read a saved property observation

curl --request GET 'https://realtycrawl.dev/v1/properties/prop_usproperty_4b825dc642cb6eb9a060e54bf8d69288' \
  --header "x-api-key: $REALTYCRAWL_API_KEY" \
  --header 'X-Max-Credits: 1'

Read a saved portal listing

curl --request GET 'https://realtycrawl.dev/v1/properties/prop_usproperty_4b825dc642cb6eb9a060e54bf8d69288/listings' \
  --header "x-api-key: $REALTYCRAWL_API_KEY" \
  --header 'X-Max-Credits: 1'

Read saved property records

curl --request GET 'https://realtycrawl.dev/v1/properties/prop_usproperty_4b825dc642cb6eb9a060e54bf8d69288/records' \
  --header "x-api-key: $REALTYCRAWL_API_KEY" \
  --header 'X-Max-Credits: 1'

Read a saved assessor sale

curl --request GET 'https://realtycrawl.dev/v1/properties/prop_usproperty_4b825dc642cb6eb9a060e54bf8d69288/transactions' \
  --header "x-api-key: $REALTYCRAWL_API_KEY" \
  --header 'X-Max-Credits: 50'

Read a saved assessor snapshot

curl --request GET 'https://realtycrawl.dev/v1/properties/prop_usproperty_4b825dc642cb6eb9a060e54bf8d69288/tax-assessments' \
  --header "x-api-key: $REALTYCRAWL_API_KEY" \
  --header 'X-Max-Credits: 1'

Read tax-roll and portal-model estimates

curl --request GET 'https://realtycrawl.dev/v1/properties/prop_usproperty_4b825dc642cb6eb9a060e54bf8d69288/valuations' \
  --header "x-api-key: $REALTYCRAWL_API_KEY" \
  --header 'X-Max-Credits: 50'
US Address Property Composite platformUS Address Property Composite API

Same key as the rest of the catalog

Get an API keyRead the docs ↗
Endpoints

What data does the US Address Property Composite API return?

JSON responses preserve the operation data and request metadata. Supported data operations also offer response field projection and CSV/NDJSON exports.

Resolve a US address property

Resolve a US street address through the assessor, recorder and portal composite.

Read a saved property observation

Read your account’s saved address-composite property observation.

Read a saved portal listing

Read the portal advertisement saved with your address-composite property, when one was observed.

Read saved property records

Read assessor, recorder-index and portal records saved with your address-composite property.

Read a saved assessor sale

Read the assessor-reported sale saved with your address-composite property, where published.

Read a saved assessor snapshot

Read the county assessor valuation snapshot saved with your address-composite property.

Read tax-roll and portal-model estimates

Read tax-roll and portal-model estimates saved with your address-composite property; not appraisals.

Comparison

How does RealtyCrawl structure US Address Property Composite data?

Keep the source context while using the same request and response conventions across your integration.

Source context and RealtyCrawl conventions
Your application needsSource contextRealtyCrawl contract
Resource identitySource-scoped resource identifierSource reference and RealtyCrawl ID
Operation dataSource-specific fields and unitsTyped resource schemas and explicit missing values
FreshnessCollection and update timesExplicit observation timestamps
Missing informationSource-dependent attributesNullable fields and field_status
CoverageOperation and market availabilityLive capabilities and source outcomes
DiagnosticsSource warnings and errorsRequest IDs and completeness metadata
AuthenticationA request to RealtyCrawlOne API key across supported platforms
FAQ

Have a question?
We got answers

Find answers to common questions about the US Address Property Composite API, credits, and coverage.

Contact us
How do I start using the US Address Property Composite API?

Get a RealtyCrawl API key, check US Address Property Composite in /v1/meta/capabilities, and send a supported request from your backend with the x-api-key header.

Are all US Address Property Composite operations available?

The catalog describes request contracts. Live enablement, accepted location selectors, and supported markets are declared per operation in /v1/meta/capabilities. Check the exact operation before running a workload.

How much does a US Address Property Composite request cost?

Source requests cost 50 credits per successful call. Saved reads cost 1 credit per observation, including successful saved-batch items. Signup includes 500 trial credits. Failed calls are refunded. Read the credit headers for the charge and remaining balance.

Will every observation contain every field?

No. Data varies by source, market, and operation. Nullable fields and field_status distinguish missing, unsupported, restricted, and temporarily unavailable values. Keep response warnings with the result.

Is a stored observation a fresh source crawl?

Stored listing, media, and history observations expire after 24 hours and do not trigger a new crawl. Inspect observed_at, source_updated_at, and response metadata to understand the age of a record.

Is this an official US Address Property Composite API?

RealtyCrawl is an independent data API and is not affiliated with US Address Property Composite. Source availability and supported operations are declared in the capabilities endpoint.

Can I use the same key for another platform?

Yes. One RealtyCrawl API key authenticates supported operations across the catalog. Check capabilities when adding a platform because availability and accepted inputs vary.