Appearance
Zillow
undefined
| Detail | Value |
|---|---|
| Category | Real Estate |
| Base URL | https://api.bridgedataoutput.com/api/v2 |
| Authentication | API Key (Query) |
| Endpoints | 6 |
| Connector key | zillow |
Using Zillow in a workflow
- Go to Connections and click New Connection.
- Pick Zillow from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | Zestimates |
GET | Properties |
GET | Media |
GET | Offices |
GET | Members |
GET | Open Houses |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Zestimates
| Detail | Value |
|---|---|
| Operation ID | zestimates_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zillow connection from the Connection dropdown.
- In the Operation dropdown, select
zestimates_0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zillow API reference.
GET
Properties
| Detail | Value |
|---|---|
| Operation ID | properties_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zillow connection from the Connection dropdown.
- In the Operation dropdown, select
properties_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zillow API reference.
GET
Media
| Detail | Value |
|---|---|
| Operation ID | media_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zillow connection from the Connection dropdown.
- In the Operation dropdown, select
media_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zillow API reference.
GET
Offices
| Detail | Value |
|---|---|
| Operation ID | offices_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zillow connection from the Connection dropdown.
- In the Operation dropdown, select
offices_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zillow API reference.
GET
Members
| Detail | Value |
|---|---|
| Operation ID | members_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zillow connection from the Connection dropdown.
- In the Operation dropdown, select
members_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zillow API reference.
GET
Open Houses
| Detail | Value |
|---|---|
| Operation ID | open_houses_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Zillow connection from the Connection dropdown.
- In the Operation dropdown, select
open_houses_5. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Zillow API reference.