A ZPID (Zillow Property ID) is the unique numeric identifier Zillow assigns to every property in its database. It appears at the end of every property page URL — the digits before _zpid — and is the most reliable key for referencing a specific home programmatically.

How do I find the ZPID for an address?

Manually: open the property's Zillow page and read the number before _zpid in the URL. Programmatically: send the address to a property data API and read the zpid field from the response — APIllow resolves addresses to full property records, ZPID included, in one call, up to 1,000 addresses per request.

Can I look up a property by ZPID?

Yes — the reverse direction works too. Send zpids as integers to the API and get the full property record back for each: address, price, Zestimate, price history, tax history, and 50+ other fields.

Do all properties have a ZPID?

Nearly every US property in Zillow's database has one, including off-market homes that have never been listed. Units in multi-family buildings get their own ZPIDs, which matters for condos and apartments: unit-level data such as photos hangs off the unit's ZPID, not the building's.

Zillow ZPID Lookup: Find the Property ID for Any Address

Every property on Zillow has exactly one stable identifier: the ZPID, or Zillow Property ID. If you're building anything on top of Zillow data — a watchlist, a comps tool, a portfolio tracker — the ZPID is the primary key you'll join everything on. This short guide covers what it is, the two manual ways to find one, and how to resolve addresses to ZPIDs programmatically at any scale.

What is a ZPID?

A ZPID is the unique numeric ID Zillow assigns to each property in its database. It's hiding in plain sight in every property page URL:

https://www.zillow.com/homedetails/1874-Bromton-Dr-Lyndhurst-OH-44124/33012456_zpid/
# the digits right before "_zpid" are the ZPID → 33012456

Three properties of the ZPID make it the right key for developers:

It's stable. Addresses get reformatted, listings come and go, prices change — the ZPID persists across all of it, including when a home goes off-market.
It's universal. Nearly every US property in Zillow's database has one, listed or not — including homes that have never been for sale in the internet era.
It's unit-level. In condos and multi-family buildings, each unit carries its own ZPID. Unit-scoped data — photos especially — hangs off the unit's ZPID, not the building's, so resolving the right ZPID is the difference between getting unit 4B's data and the building's.

Finding a ZPID manually

For one property, you don't need any tooling:

From the URL: search the address on Zillow, open the property page, and read the digits before _zpid at the end of the URL.
From the page source: view source and search for zpid — it appears in the page's embedded data, useful when a URL got shortened or mangled in a spreadsheet.

This stops scaling at about the tenth property. For lists, resolve programmatically.

Address → ZPID, programmatically

Send addresses; get full property records back, ZPID included. Up to 1,000 per request:

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"]}'

# response (excerpt):
{
  "zpid": 33012456,
  "address": "1874 Bromton Dr, Lyndhurst, OH 44124",
  "home_status": "SOLD",
  "price": ..., "zestimate": ..., "price_history": [...]
}

Because the resolver returns the whole record, "look up the ZPID" and "get the property data" are the same call — you're not paying twice. Address matching is strict by design: if an input address can't be confidently resolved to the right property, you get an explicit error for that entry rather than a silently wrong house. With messy CRM exports, that guarantee matters more than it sounds.

ZPID → property, the other direction

Already have ZPIDs — from URLs you collected, a previous export, or another dataset? Send them as integers:

curl -X POST https://api.apillow.co/v1/properties \
  -H "x-api-key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"zpids": [33012456, 20794780]}'

Zillow URLs work as inputs too ({"urls": [...]}) — the ZPID is parsed out for you. All three input types can be mixed across a batch, which is convenient when your list is half addresses, half pasted URLs.

What developers build on ZPIDs

Pattern	How the ZPID is used
Watchlists & alerts	Store ZPIDs, re-poll on a schedule, diff `price` and `home_status` against the last pull
Dataset joins	Use the ZPID as the join key between Zillow fields and county records, rent rolls, or CRM rows — more reliable than address-string matching
Comps & analysis	Dedupe candidate lists by ZPID before pulling sold data and price history
Condo/unit data	Resolve the unit-level ZPID to get unit-scoped photos and details in multi-family buildings

Resolve your first address now

Free tier, no credit card. Address in, ZPID and 50+ fields out.

Get API Key

Final takeaway

The ZPID is Zillow's primary key, and it should be yours too: stable across listings, universal across on- and off-market homes, and precise down to the unit. Read it from a URL when you need one; resolve addresses through the API when you need a thousand.