Zillow Signal Monitor Setup Guide

Time: 10 minutes | Difficulty: Moderate | Market: Real Estate Mode: Signal-only | API: Restricted public API / Third-party data providers | Docs: zillow.com/howto/api/APIOverview.htm

This guide configures a Zillow real estate signal monitor using the botwir3 runtime. Connect to property data sources, generate real estate market signals locally, and review them before acting manually.

Signal-only mode

Zillow does not support automated transactions through an API. The Zillow API provides property data but no transactional capability — real estate transactions are inherently manual (offers, inspections, closings). This guide configures the botwir3 runtime in signal-only mode: the bot monitors property data and generates signals. The user reviews the signals and acts manually.

botwir3 does not place offers, bids, or transactions on Zillow. The user is responsible for all execution decisions.

Before you start

Verify that data access is permitted under Zillow's current terms of service before deploying. botwir3 provides tools for building structured automation. The user is responsible for compliance with the platform's terms and all applicable regulations.

Zillow Terms of Use | Last verified: May 2026

What you need

• A Zillow account (for manual property research and outreach)
• A data source for property information (Zillow API, ATTOM, Bridge Interactive, or public records)
• The botwir3 runtime downloaded and unzipped
• A strategy config file from the builder (signal-only mode)

Step 1: Configure the data source

Zillow's public API has restricted access. Third-party data providers offer comparable property data:

Create adapter.json in the bot directory:

{
  "adapter": "zillow",
  "mode": "signal_only",
  "data_source": {
    "type": "api",
    "provider": "attom",
    "api_key": "paste-data-provider-api-key-here",
    "region": "70301"
  },
  "rate_limit_ms": 300000
}

region: ZIP code or FIPS code for the target market.

rate_limit_ms: Real estate data changes slowly. 300000ms (5 minutes) is a reasonable polling interval.

API keys (for the data provider) are stored in a local config file on the machine running the bot. They are not transmitted to botwir3 or any third party. botwir3 never sees, stores, or has access to platform credentials.

Step 2: Configure signal output

{
  "signal_output": {
    "type": "file",
    "path": "./signals/zillow.json"
  }
}

Step 3: Start the monitor

botwir3 start --config my-strategy.json --signal-only

Expected output:

[botwir3] Adapter: zillow
[botwir3] Mode: signal-only
[botwir3] Data source: attom (region: 70301)
[botwir3] Polling interval: 300s
[botwir3] Monitoring...

The runtime evaluates signals against the strategy and logs opportunities. It does not connect to Zillow for transaction execution. The gate function compares proposed signals against the configured spec. All signals are recorded in the local ledger.

Reading the signals

[botwir3] Signal: UNDERVALUED | 123 Main St, Thibodaux LA | Listed: $185,000 | Model: $215,000
[botwir3] Signal logged to ./signals/zillow.json

The user reviews each signal and decides whether to pursue the property manually — contacting the listing agent, scheduling a viewing, or submitting an offer through standard real estate channels.

Why signal-only?

Zillow does not provide a transactional API. Real estate transactions require manual processes: offers, counteroffers, inspections, title searches, and closings. The Zillow API (where available) provides property data and estimates. Third-party providers (ATTOM, Bridge Interactive) offer comparable data for programmatic access. The bot identifies opportunities; the user executes.

Related guides

• Redfin Signal Monitor Setup Guide — real estate, signal-only
• Shopify Setup Guide — e-commerce, full automation (seller-side)
• TradingView Webhooks Setup Guide — route alert signals to any adapter

One bot. $129. No subscription. No $749/mo platform. → Build for Zillow