Opendoor

undefined

Detail	Value
Category	Real Estate
Base URL	https://api.opendoor.com/v1
Authentication	OAuth2
Endpoints	5
Connector key	opendoor

Using Opendoor in a workflow

1. Go to Connections and click New Connection.
2. Pick Opendoor from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET	Offers
GET	Listings
GET	Tours
GET	Markets
GET	Address Validation

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Offers

Detail	Value
Operation ID	offers_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Opendoor connection from the Connection dropdown.
3. In the Operation dropdown, select offers_0.
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 Opendoor API reference.

GET

Listings

Detail	Value
Operation ID	listings_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Opendoor connection from the Connection dropdown.
3. In the Operation dropdown, select listings_1.
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 Opendoor API reference.

GET

Tours

Detail	Value
Operation ID	tours_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Opendoor connection from the Connection dropdown.
3. In the Operation dropdown, select tours_2.
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 Opendoor API reference.

GET

Markets

Detail	Value
Operation ID	markets_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Opendoor connection from the Connection dropdown.
3. In the Operation dropdown, select markets_3.
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 Opendoor API reference.

GET

Address Validation

Detail	Value
Operation ID	address_validation_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Opendoor connection from the Connection dropdown.
3. In the Operation dropdown, select address_validation_4.
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 Opendoor API reference.