Permit Data vs. Property-Owner Data: Why They're Not the Same Thing

One of the most common questions we get is some version of: "I bought permit data, so where's the owner's name and mailing address?" It's a fair question, and the answer surprises people: a building permit usually doesn't contain the property owner's contact information at all. Here's what's actually in permit data, why owner data is a separate and much harder dataset, and how to get each one.

What's actually in a building permit

A building permit is a public record a city or county creates when someone does construction work. It typically contains the property address, a description of the work (re-roof, solar install, kitchen remodel), the permit type and status, the key dates (applied, issued, finaled), an estimated job value, and often the contractor who pulled it. That's the raw building-activity data, and it's genuinely useful: it tells you what work is happening, where, when, and how big.

What's usually NOT in a building permit

What a permit generally does not include is the legal property owner's name and mailing address. Permits are about the work, not the owner of record. Some jurisdictions list an "applicant" or "owner" field, but it's inconsistent, frequently the contractor or a company, and almost never a reliable mailing address you could actually send a letter to.

So if your goal is to mail or call the homeowner, the permit alone won't get you there. You need a second dataset.

Where owner data actually comes from

The property owner of record lives in county assessor and tax-roll data, not in the permit system. Every county maintains an assessment roll that ties each parcel to its owner and the owner's mailing address (which is often different from the property address, in the case of landlords and absentee owners). To connect the two, you match the permit to the assessor record for the same property, usually by parcel number or normalized address.

Why that's a hard, separate product

Matching permits to owners sounds simple until you do it across the whole country. A few reasons it's genuinely difficult:

• It's county by county. There are thousands of assessor systems, each with its own parcel format, field names, and access method. There is no single national feed.
• Parcel keys don't line up. The parcel number on a permit and the one in the assessor roll are often formatted differently, or the permit carries an account number instead of the parcel ID, so the join takes real normalization work.
• Redaction laws are spreading. A growing number of states now remove owner names from public property data for privacy. New Jersey, for example, bars owner names from its public tax-roll downloads under Daniel's Law. The mailing address often survives, but the name may not.
• Coverage is uneven. Some counties publish clean, current rolls; others are stale, partial, or lock the data behind bot-walls.

That stitching work, and the coverage gaps it creates, is exactly why owner contact data isn't baked into a flat permit API. It's a distinct product with its own pipeline.

How to get each one

For permit data (the records themselves), use the Permit API or a no-code Bulk Data Export. That gives you the address, work type, dates, value, and contractor across 7,000+ U.S. cities.

For owner contact data (mailing addresses of homeowners worth reaching), use Contractor Leads. We do the assessor matching for you and deliver ready-to-mail leads in an exclusive ZIP and trade, owner mailing address included, one contractor per territory. Where a state redacts owner names, we're upfront about it and provide the mailing address so you can still reach the property.

Not sure which you need? We wrote a short guide: Which PermitStack Product Do You Need?