RealtyCrawl
Zillow platformZillow

Resolve a Zillow source property

Resolve one exact current NYC non-condominium tax lot from official DCP PLUTO. Supply parcel_id=ten-digit BBL, jurisdiction=US-NY-NYC,country=US; alternatively platform=nyc_pluto,native_id=BBL,country=US. No address/geocoder, condo billing/unit-lot or historical split/merge inference. Success costs50 credits and stores account-owned property/record/assessment observations24h. Confidence unknown, method exact_current_nyc_tax_lot_bbl. Source: NYC Open Data DCP PLUTO. Independent wrapper, no title/ownership/unit/availability verification. Zillow alternative:resolve platform=zillow,native_id=ZPID,country=US directly for an Austin single-family sale home. No prior listing lookup;independently validated native identity,bare canonical URL,market,type,status and USD asking price. Source update time unknown;observed_at is retrieval. Private24h property and associated advertisement reads cost1credit;source resolution50,errors/replay0. No address geocoding,cadastral/cross-platform match or history guarantee.

Get an API keyRead the docs

Use a resource previously observed by this account. Check live capabilities for accepted source scope before calling.

Try this operation

Selectors expire after 24 hours. Preserve source meanings and inspect response warnings.

Zillow API
1 endpoint 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 "content-type: application/json" \
  -d '{"platform":"zillow","native_id":"29419686","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.

Request and response

Illustrative contract examples; source availability and values can change.

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 '{"platform":"zillow","native_id":"29419686","country":"US"}'

Illustrative response

{
  "data": {
    "status": "matched",
    "candidates": [
      {
        "id": "prop_zillow_9ccca0ad8b2d8cea1b7e7756",
        "entity_type": "property",
        "confidence": null,
        "method": "exact_source_zillow_zpid",
        "source": {
          "platform": "zillow",
          "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": "unknown",
    "sources": []
  }
}
FAQ

Have a question?
We got answers

Source scope and credit handling

Contact us
Does this establish current availability or value?

Read the operation-specific source limits above. Calendar status is not occupancy or a booking guarantee. Dated hotel prices are partial offer observations. Zillow identity is source-scoped, without cadastral or cross-portal matching. Comparable homes are unadjusted provider recommendations; their price meaning is unknown and they are not verified sales or appraisals.

How are credits handled?

Source calls cost 50 credits. Retained property and associated-advertisement reads cost 1. Errors and existing idempotent replays cost zero. A replay is a prior response snapshot and can outlive selector retention.