Zillow

Zillow is a leading online real estate marketplace that helps users buy, sell, rent, and discover properties. It provides extensive property listings, home value estimates, and real estate data for homes across the United States.

Power end-to-end data operations for your Zillow API with Nexla. Our bi-directional Zillow connector is purpose-built for Zillow, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Zillow or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Zillow workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Zillow credential, you need to obtain your Zillow Web Services ID (ZWS ID) from your Zillow account. Zillow uses API key authentication for all API requests, with the ZWS ID sent as a URL parameter.

To obtain your Zillow Web Services ID, follow these steps:

1. Sign in to your Zillow account using your administrator credentials, or create a new account at Zillow.

2. Navigate to the Zillow Web Services page or visit the Zillow API documentation to access API key management.

3. In the Zillow Web Services portal, navigate to Get API Key, Register for API Access, or API Key Management to access your API key management.

4. If you don't have a ZWS ID yet, click Register or Get API Key to create a new ZWS ID.

5. Complete the registration process:

   • Enter your contact information
   • Agree to the Zillow API Terms of Service
   • Specify your intended use of the Zillow API
   • Click Submit or Register to complete registration

6. After registration is complete, your Zillow Web Services ID (ZWS ID) will be displayed. Copy the ZWS ID value immediately, as it may not be accessible again after you navigate away from the page.

7. Store the ZWS ID securely, as you will need it to configure your Nexla credential. The ZWS ID is sensitive information and should be kept confidential.

The ZWS ID is sent as a URL parameter (zws-id) for all API requests to the Zillow API. The key authenticates your requests and grants access to Zillow resources based on your account permissions. If your ZWS ID is compromised, you should immediately contact Zillow support to revoke it and generate a new one. For detailed information about obtaining ZWS IDs, API authentication, and available endpoints, refer to the Zillow Web Services documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Zillow Web Services ID	No	Yes	Zillow Web Services ID

Create a credential in Nexla

Zillow uses Zillow Web Services ID (ZWS ID) authentication for all API requests. The ZWS ID is sent as a URL parameter (zws-id) in API requests.

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Zillow

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Zillow Web Services ID in the Zillow Web Services ID field. This is your Zillow Web Services ID from your Zillow account, obtained in Prerequisites. The ZWS ID is sent as a URL parameter (zws-id) for all API requests to the Zillow API and must be kept confidential.

   Your Zillow Web Services ID (ZWS ID) can be found in the Zillow Web Services portal after registering for API access. The ZWS ID is sent as a URL parameter (zws-id) for all API requests to the Zillow API.

   If your ZWS ID is compromised, you should immediately contact Zillow support to revoke it and generate a new one. The ZWS ID provides access to your Zillow account data and should be treated as sensitive information. Keep your ZWS ID secure and do not share it publicly.

   For detailed information about obtaining ZWS IDs, API authentication, and available endpoints, see the Zillow Web Services documentation.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Zillow connector tile, then select the credential that will be used to connect to the Zillow instance, and click Next; or, create a new Zillow credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Zillow endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get subregions for a state

This endpoint template gets a list of subregions for any state from the Zillow API. Use this template when you need to access regional data, geographic information, or subregion metadata for analysis, reporting, or integration purposes.

• Enter the State for fetching subregions in the State for fetching subregions field. This should be the state code of the region to retrieve subregions from (e.g., AL for Alabama, CA for California). The default value is AL. The State code determines which state's subregions will be retrieved.
• Select the Subregion Type from the Subregion Type pulldown menu. This should be the type of subregions to retrieve. Available options are: county, city, zipcode, or neighborhood. The default value is county. The Subregion Type determines which type of subregions will be retrieved.

This endpoint returns a list of subregions for any state from the Zillow API, including subregion IDs, names, and other geographic metadata. The endpoint supports retrieving counties, cities, zipcodes, or neighborhoods as subregions.

For detailed information about regional data, API response structures, and available subregion data, see the Zillow Web Services documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Zillow data sources can also be manually configured to ingest data from any valid Zillow API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Zillow API endpoints typically follow the pattern https://www.zillow.com/webservice/{endpoint_name}?zws-id={zws_id}&{parameters}, where {endpoint_name} is the endpoint name and {zws_id} is your Zillow Web Services ID. Zillow API responses are returned in XML format by default; for example, a response with nested elements like response/list/region would use the path *//response[*]//list//region in the Set Path to Data in Response field. For a complete list of available Zillow API endpoints, see the Zillow Web Services documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Zillow data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.