Listing Contact & Tour Options

View all Redfin Property Data endpoints →

The engagement-funnel metadata for a listing, keyed by propertyId/listingId: which contact and tour actions the listing supports (agent contact paths, tour eligibility and related conversion options). Check it before building scheduling or inquiry integrations so your flow only offers actions the listing actually supports.

API Features

Action eligibility Reveals which contact/tour actions exist for the listing before you offer them.
Integration pre-flight Validate scheduling assumptions per listing instead of per market.
Funnel metadata Conversion-path fields support engagement analytics per property.
Consistent keying propertyId/listingId keys align with all other detail endpoints.

Live API Demo

GET /api/project/redfin/customer-conversion-info

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/redfin/customer-conversion-info?key=<API_KEY>&propertyId=40775351&listingId=224185786'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Why call this endpoint first?

Different listings support different contact and tour actions; checking eligibility first avoids showing users booking or inquiry entries that are not actually available.

Does the response include contact details?

It returns action eligibility and funnel metadata, not private contact details; for agent identity use the listing-agent endpoint.

Must I call it every time?

During integration, spot-check per listing; re-check a listing when its action eligibility changes.

Related operations

Guides

View Subscription Plans →