Bridge Interactive API: Requirements, Access, and What to Use While You Wait

August 19, 2026 · 7 min read

When Zillow retired its public API in 2021, it didn't leave developers with nothing — it pointed them at Bridge Interactive, its own data platform. If you've been told "just use Bridge," this is the guide to what that actually involves: what Bridge serves, the two very different gates you have to get through, and the honest answer to whether you — an indie developer, a startup, a proptech team without an MLS membership — can realistically use it.

Short version: Bridge is real, it's still Zillow's official path, and whether you can get in depends entirely on which data you need. Let's break it down accurately, because most write-ups get the nuance wrong.

What Bridge Interactive actually is

Bridge Interactive is a developer data platform owned and operated by Zillow Group (Zillow acquired it in 2016). It exists to give approved developers programmatic access to real estate data, and it splits cleanly into two tracks:

Track What it serves Delivered via
MLS listing data Active/sold listings from MLSs across the US & Canada RESO Web API (OData) + legacy RETS
Zillow Group datasets Public Records (~148M properties, 3,200 counties), Zestimates & Rent Zestimates, and economic data Bridge REST APIs

These are governed by different rules, and conflating them is where most guides go wrong. The gate you face is completely different depending on which one you need.

Track 1: MLS listing data — the real wall

This is the track people mean when they say Bridge is "enterprise-only," and for this track it's essentially true. To get MLS listing data, Bridge's own guidance is to "reach out to your local Multiple Listing Service and request data access using the Bridge API." And a developer who emailed Bridge support in 2025 got this reply, quoted verbatim:

"In order to receive data from an MLS/Board or Local Association, you must be a paying member or an approved vendor with the MLS/Board or Association that you're looking to request data from."

That's the wall. Access to MLS data is, in Bridge's words, "entirely at the discretion of the MLS," and each one has its own process, criteria, license agreements, and potentially fees. If you're a broker, an MLS member, or an approved vendor, this path is open to you. If you're an indie developer or a startup that just wants listing data, you generally are not eligible — not because Bridge rejected you, but because you don't have the MLS relationship that Bridge requires as a precondition.

Track 2: Zillow's own datasets — open to apply, but tightly capped

Here's the nuance almost everyone misses: Zillow's own datasets — Public Records, Zestimates, economic data — are open to the public to apply for. You don't need an MLS membership for these. Bridge says so directly: "Is registration for Zillow datasets open to the public? Yes."

But "open to apply" is not "open to use freely." The terms on this track are restrictive:

For a lot of real projects — an investor tool that scores deals, a CRM that enriches leads, anything that needs to keep the data — the no-storage rule alone is a dealbreaker, membership or not.

A quick word on RESO, since you'll hit it

On the MLS track you'll see "RESO Web API" everywhere. RESO (the Real Estate Standards Organization) publishes a common data schema and an OData v4–based REST standard so that every MLS's feed looks the same to developers. Bridge is a Platinum-certified RESO Web API provider — it normalizes each MLS's data to the RESO Data Dictionary and serves it through one standard interface. It's genuinely good engineering; it just sits behind the membership gate above.

So can you actually use Bridge?

An honest decision guide:

You are… Bridge fit
A brokerage or MLS member needing listing data Good fit — go through your MLS
An approved MLS vendor Good fit for that MLS's data
Building a display-only widget showing Zestimates with a link back to Zillow Workable — apply for the Zillow datasets track, mind the 1,000/day cap
An indie dev / startup that needs to store or analyze property data Poor fit — the membership gate or the no-storage rule will stop you

What to use if Bridge won't work for you

If you landed in that last row, you're exactly who the third-party API ecosystem exists for. The tradeoff is straightforward: Bridge gives you licensed, official data under restrictive terms and a membership gate; a provider like APIllow gives you Zillow-style property data as JSON you can actually store and build on, with a key issued in about a minute and no MLS relationship required.

APIllow returns 50+ fields per property — price, Zestimate and Rent Zestimate, price and tax history, sold data including the sale date, schools, photos — for any US address, ZPID, or Zillow URL:

curl -X POST https://api.apillow.co/v1/properties \ -H "x-api-key: YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{"addresses": ["1874 Bromton Dr, Lyndhurst, OH 44124"]}'

No use-case review, no 1,000/day dataset cap, no display-only restriction. It's not a replacement for licensed MLS data if you specifically need the MLS feed — nothing outside the MLS system is — but for the property data most developers actually want, it's the path that doesn't require a membership you don't have. The full landscape is in our unofficial Zillow API guide and the alternatives roundup.

Can't get through the Bridge gate?

Property data as storable JSON, key issued in 60 seconds. Free tier, no membership, no review queue.

Get API Key

Related reading

Final takeaway

Bridge Interactive is alive and it's Zillow's official developer path — but "use Bridge" hides two very different gates. MLS listing data needs an MLS membership or vendor status; Zillow's own datasets are open to apply for but are capped and display-only. If you need property data you can store and build on without a membership, that's precisely the gap a third-party API fills — and why so many developers who start at Bridge end up somewhere else.