Zillow Python API Docs | dltHub

Zillow Group API is a platform that provides access to MLS listings, performance reporting, reviews, and transaction management data via RESTful endpoints. The REST API base URL is https://bridgedataoutput.com and Bridge endpoints use API access tokens; Reporting API uses OAuth 1.0 (any consumer key, secret ‘none’); Transaction API uses OAuth 2.0 (3‑legged)..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Zillow data in under 10 minutes.

---

What data can I load from Zillow?

Here are some of the endpoints you can load from Zillow:

---

How do I authenticate with the Zillow API?

Bridge requests require an access token passed as a header (e.g., Authorization: Bearer <token>). Reporting API requires OAuth 1.0 parameters (consumer key and secret) and Transaction API requires a bearer token obtained via OAuth 2.0.

1. Get your credentials

1. Navigate to https://bridgedataoutput.com/register and create a Bridge Interactive Platform account.
2. After account approval, log in to the Bridge Dashboard.
3. Go to Data Access > API Access Tokens.
4. Click Create New Token, give it a name, and copy the generated token.
5. Store the token securely for use in API calls.

2. Add them to .dlt/secrets.toml

Copy
[sources.zillow_source]
api_key = "your_bridge_access_token"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.

---

How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

Copy
dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Zillow API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

Copy
python zillow_pipeline.py

If everything is configured correctly, you'll see output like this:

Copy
Pipeline zillow_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset zillow_data
The duckdb destination used duckdb:/zillow.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

Copy
dlt pipeline zillow_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.

---

Python pipeline example

This example loads listings and reports from the Zillow API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def zillow_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://bridgedataoutput.com",
            "auth": {
                "type": "api_key",
                "api_key": api_key,
            },
        },
        "resources": [
            {"name": "listings", "endpoint": {"path": "listings", "data_selector": "value"}},
            {"name": "reports", "endpoint": {"path": "reports", "data_selector": "listings"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="zillow_pipeline",
        destination="duckdb",
        dataset_name="zillow_data",
    )
    load_info = pipeline.run(zillow_source())
    print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.

---

How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("zillow_pipeline").dataset()
sessions_df = data.listings.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM zillow_data.listings LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("zillow_pipeline").dataset()
data.listings.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.

---

What destinations can I load Zillow data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authentication Errors

• 401 Unauthorized – Occurs when the access token is missing, expired, or not authorized for the requested MLS/Office ID. Ensure the token from the Bridge Dashboard includes the required dataset codes.
• 403 Forbidden – May indicate that your account lacks permission for the requested resource or that the MLS has not approved your access.

Rate Limits & Pagination

• Listing pagination – The RESO Web API returns a default of 10 records; use $top (max 200) to increase per request. For larger extracts, use replication endpoints as described in the Bridge docs.
• Performance reporting – The reports summary endpoint returns a maximum of 1,000 listings per call. Use the from query parameter to page through additional sets (e.g., from=1000).
• Rate limiting – Exceeding allocated request quotas will result in HTTP 429 responses; throttle requests accordingly.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.

---

Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

• data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
• dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack