The best Zillow APIs in 2026, tested on the same 12 listings

You have a Zillow link, or a few thousand of them, and you need the price, the beds and baths, the photos, and the price history as JSON. Maybe it's an investor dashboard or a comps tool. Maybe an agent is filling in a spreadsheet. Zillow doesn't sell that as a self-serve API, so you're choosing between hosted APIs that read Zillow's pages for you, or applying to Zillow's partner program and waiting.

Four of the options below got the same 12 active for-sale homes in Austin, Columbus, and Seattle on September 30, 2026. That's one property lookup per API per home, checked against 16 fields a property app would use. Apify's Zillow actor and Zillow's own Bridge Interactive program are covered from their pages.

Here's who each one suits.

The best Zillow APIs

• HasData for the full record at steady volume
• OpenWeb Ninja for a flat monthly plan with every raw field
• Zillapi for a small project with a tidy schema
• AnyAPI for cheap listing checks at high volume
• Apify for batch jobs you schedule yourself
• Bridge Interactive for licensed Zestimates and public records

What makes a good Zillow API?

I'm assuming you're a developer who already has Zillow URLs or zpids (Zillow's property IDs) and needs each home's details in your own database. You aren't building a Zillow clone. You want the record for a known property, and you want it to be right. Here's what I compared.

• The fields you'd otherwise scrape. Sixteen fields were checked on every home: list price, beds, baths, living area, lot size, year built, home type, listing status, days on market, photos, description, coordinates, price history, tax records, listing agent, and schools.
• Numbers you can use as they arrive. A bath count or a Zestimate that's wrong or missing breaks a valuation model quietly. Every API's values were compared against each other and against Redfin's record for the same home.
• Price at your volume. Every price below is for 10,000 single-property lookups a month, on monthly billing.
• Speed and response size. A comps tool that looks up twenty homes on a click cares about seconds. A pipeline that stores every response cares about whether a lookup is 26 KB or 237 KB.

The best Zillow APIs at a glance

The same 12 homes went through each API on September 30, 2026, one property lookup per home. Here's what came back.

Every API returned a Zestimate on 1 of the 12 homes, the same one, and every rounded bath count was half a bath above Redfin's on the same 5 homes.

Best Zillow API for the full record at steady volume

HasData

HasData pros:

• 188 of 192 fields filled, the most of any option, and its four misses were on the two homes where every other API came back empty too
• Tied for the fastest median at 3.4 seconds, and the slowest of its 12 calls took 4.5
• A 26 KB response, compact enough to store whole

HasData cons:

• No small paid plan: after the free 200 lookups, the next step up is 40,000 a month
• A Zillow lookup costs 5 credits, so the free 1,000 credits a month is 200 lookups

If you want the whole Zillow record and you'll use it every month, HasData is the pick. Every call came back with the same predictable shape: price, beds, baths, area, the price history with sale events, nearby schools with ratings, the listing agent with phone and license number, and a resoData block with the MLS facts, including full and half baths as separate numbers.

The only home where HasData filled more than the others was 122 W North Broadway in Columbus, where Zillow's tax history was empty but the MLS facts carried an annual tax amount. That's the kind of difference you only see when you run the same homes through all three.

The catch is the plan. HasData prices by credits, and a Zillow property lookup is 5 of them, so read the Zillow row on the pricing page rather than the credit count. Below about 21,000 lookups a month, OpenWeb Ninja's $25 plan with its overage is the cheaper way to the same facts.

HasData pricing: On HasData's Zillow API page on September 30, 2026: a free plan with 1,000 credits a month (200 Zillow lookups), no card. Paid plans from $59 a month for 40,000 Zillow requests on monthly billing, which is $1.47 per 1,000.

Best Zillow API for a flat monthly plan with every raw field

OpenWeb Ninja

OpenWeb Ninja pros:

• Returns 177 top-level fields per home, including Zillow's foreclosure, tour, and rental estimate fields
• Steady speed, with every call between 3.0 and 5.6 seconds

OpenWeb Ninja cons:

• A median response of 237 KB, about nine times HasData's for the same facts
• The free plan is 100 requests a month with a hard stop

OpenWeb Ninja's Real-Time Zillow Data API gives you what's on Zillow's property page as Zillow structures it. You call /property-details with a zpid or URL and an x-api-key header, and you get the whole page object back, from resoFacts to nearbyHomes to mortgage rate tables.

That's its strength and its cost. Nothing is missing, because nothing was trimmed. But you'll write your own mapping, and a pipeline that stores every response stores about a quarter of a megabyte per home. If you only need twenty fields, you're paying in bandwidth and parsing for the other 157.

For a steady 10,000 lookups a month, the $25 Pro plan is the best price among the three Zillow-specific APIs. Past about 21,000 a month, the $0.003 overage makes HasData's $59 plan cheaper.

OpenWeb Ninja pricing: On OpenWeb Ninja's plan page on September 30, 2026: Basic is free for 100 requests a month. Pro is $25 a month for 10,000, then $0.003 each. Ultra is $75 for 50,000. Pay as you go is $0.005 a request.

Best Zillow API for a small project with a tidy schema

Zillapi

Zillapi pros:

• The cleanest response of the three: nested listingPrice, listingAddress, agent, and mls objects, and bathroomsFull and bathroomsHalf alongside the rounded count
• 100 free credits at signup with no card, and a failed call costs nothing
• Separate endpoints for photos, price history, tax history, and schools, at 1 credit each, so you can fetch just the slice you need

Zillapi cons:

• Slowest in the test, with a 6.9 second median and two calls over 11 seconds
• The 100 free credits are one-time, and top-ups need a paid plan
• The pricing page and the plan picker disagree on the price

Zillapi is the API I'd hand to someone building a first version this weekend. A property lookup by URL costs 1 credit, the response headers tell you what was charged and what's left, and the JSON reads like someone designed it rather than copied it from Zillow's page.

It returned the same values as HasData and OpenWeb Ninja on every home for price, beds, baths, area, lot size, year built, status, and days on market. Where it's weaker is speed and price at volume. Ten thousand lookups a month means the $5 plan plus nine $4 top-ups, which is $41, against $25 at OpenWeb Ninja. Below about 6,000 lookups a month, Zillapi is the cheaper of the two.

One thing to check before you pay. The pricing page lists the Monthly plan at $5 a month and the annual plan at $54 a year. The plan picker shown right after signing up listed Monthly at $10 and Annual at $100 a year. The credit counts matched. The prices didn't.

Zillapi pricing: On Zillapi's pricing page on September 30, 2026: Free is 100 credits once, no card. Monthly: $5 a month for 1,000 credits on the pricing page ($10 in the signup plan picker), top-ups $4 per 1,000. Annual: $54 a year on the pricing page ($100 in the plan picker), top-ups $3 per 1,000. A lookup by URL or zpid is 1 credit, by address 3.

Best Zillow API for cheap listing checks at high volume

AnyAPI

AnyAPI pros:

• Billed per request from a prepaid wallet: no plan, no minimum, nothing that expires
• A small normalized response, about 6.5 KB, with price, status, beds, baths, area, photos, description, coordinates, and the Zestimate fields
• The same key does Redfin by URL with redfin.property, which adds year built, lot size, the listing agent, and fractional baths

AnyAPI cons:

• The Zillow lookup leaves out year built, lot size, price history, tax records, the listing agent, and schools on every home
• Its baths field repeats Zillow's rounding, with no full and half split
• Two of its 12 calls took 21.1 and 38.5 seconds
• It reported 0 days on market for two homes that every other API, and its own search endpoint, put at 3 and 7 days

AnyAPI's zillow.property is built for checking a lot of listings often: has the price changed, and is it still for sale. For that job it's the lowest bill on this page below about 148,000 lookups a month, and 10,000 lookups a month cost $8.00. Past that, HasData's $119 plan for 200,000 is cheaper.

It isn't the full record. It filled 120 of the 192 fields, and adding a Redfin call per home brought that to 154, still with no price history, tax records, or schools. If your product shows a home's sale history or its school ratings, HasData, OpenWeb Ninja, or Zillapi will save you a second source.

The speed was uneven. Ten of the twelve calls took between 2.6 and 5.5 seconds, and two took 21.1 and 38.5. For a nightly job that's fine. For a page a user is waiting on, set a timeout and retry.

AnyAPI pricing: $0.80 per 1,000 Zillow lookups from a prepaid wallet, rising to $2.64 per 1,000 for a lookup the cheapest source can't answer and a backup does. Redfin lookups are $0.80 per 1,000. New accounts get free credit, no card required.

Best Zillow API for batch jobs you schedule yourself

Apify

Apify pros:

• Billed per home returned, so a small weekly job costs little
• $5 of free usage every month on the free plan
• Scheduling, dataset storage, and exports to JSON, CSV, or Excel are built in

Apify cons:

• You run a job and collect a dataset, rather than calling an endpoint and getting one home back
• The listed price is a "from" price

Apify is a marketplace of scrapers, and its Zillow Detail Scraper takes a list of Zillow URLs and writes each home to a dataset. That suits a weekly export of a few thousand homes into a spreadsheet or a warehouse. It suits a per-request API less, because each lookup is a job run.

Apify pricing: On the actor's Apify page on September 30, 2026: $5 of free usage a month on the free plan. The Zillow Detail Scraper is listed from $1.70 per 1,000 results, and the Zillow Search Scraper from $1.30 per 1,000.

Best Zillow API for licensed Zestimates and public records

Bridge Interactive

Bridge Interactive pros:

• Zillow's own program, with a Zestimates API, a public records API covering about 148 million properties, and Zillow's housing market data
• Clear written terms on what you may do with the data

Bridge Interactive cons:

• Every application is reviewed, and approval isn't guaranteed
• You can't store what you pull, you must link back to Zillow, and the limit is 1,000 calls a day per dataset

If you're a brokerage, an MLS vendor, or a product that only displays live Zillow data next to a link to Zillow, apply to Bridge Interactive. Zillow Group owns it.

Most readers of this page will skip it, for two reasons. The terms say you may only retrieve and display data, not store it, which rules out a database of homes. And the Zestimates API returns the Zestimates available on Zillow.com, so it can't give you the ones Zillow doesn't show. On the 12 homes here, that was 11 of them.

If you only need market-level numbers, like home value or rent indexes by ZIP code, Zillow publishes those as research data downloads, which Zillow says have looser terms on storing the data. Bridge's Econ Data API serves the same metrics.

Bridge Interactive pricing: No price on Bridge's Zillow Group Data page on September 30, 2026. Access is by application, and approved accounts get up to 1,000 calls a day per dataset.

Which Zillow API should you use?

• You need the full record, including price history, schools, and taxes, at more than about 21,000 lookups a month: HasData.
• The same full record at a steady 10,000 a month, and you're fine parsing Zillow's raw page object: OpenWeb Ninja.
• A prototype or a small tool under about 6,000 lookups a month, and you want a clean schema: Zillapi.
• Frequent checks of price and status across a large list of homes: AnyAPI.
• A weekly export into a spreadsheet or warehouse, run on a schedule: Apify.
• You're a brokerage or MLS vendor and only display live data: Bridge Interactive.
• Market trends by ZIP code rather than individual homes: Zillow's research data downloads.

Whichever you choose, don't read bathrooms as the truth, and don't expect a Zestimate on most active listings. The Zillow API page has the live request format and the current price, and the Redfin API page covers the same homes from Redfin.

Frequently asked questions

Does Zillow have a public API?

Not one you can sign up for and call today. Zillow's developer site lists a Zestimates API behind a request-access form, documented on Bridge Interactive's platform, and Bridge reviews each application against its terms. Approved accounts get up to 1,000 calls a day per dataset, can't store what they pull, and have to link back to Zillow.

Can I get the Zestimate through an API?

Only where Zillow shows one. Bridge's Zestimates API returns the Zestimates available on Zillow.com, and the hosted APIs read the same page. Across three ZIP codes on 2026-09-30, Zillow showed a Zestimate on 26 of 75 for-sale listings, and on 1 of the 12 homes run through every API here.

How much does a Zillow API cost?

For 10,000 property lookups a month on monthly billing, prices on 2026-09-30 were $25 at OpenWeb Ninja (Pro plan), $41 at Zillapi ($5 plan plus nine $4 top-ups), $59 at HasData (a plan that covers 40,000), from $17 at Apify, and $8.00 at AnyAPI, billed per request. Bridge Interactive publishes no price.

Which Zillow API returns the most fields?

HasData, by one value. On 12 for-sale homes tested 2026-09-30, HasData filled 188 of 192 field values, OpenWeb Ninja and Zillapi 187 each, and AnyAPI's Zillow lookup 120. The three Zillow-specific APIs missed values on the same homes; HasData's extra one is a tax amount from the listing's MLS facts.

Why does Zillow's bath count differ from Redfin's?

Zillow's rounded bath count counts a half bath as a full one. On 5 of the 12 homes tested on 2026-09-30, Zillow said 2 where Redfin said 1.5, or 3 where Redfin said 2.5. Zillapi's bathroomsFull and bathroomsHalf fields, and HasData's resoData block, carry the split.

Use data responsibly and follow AnyAPI's Acceptable Use Policy.