Arizona building permit data
Markets on record
10Permits on record
61,372Available
10Buy a market
Weekly feed. Every permit in the market, every week. The first delivery carries the last 13 weeks, then it arrives every Sunday.
Full history. Everything we hold for the market in one file, bought once.
Files include every trade and work type. Filter to yours in one click.
Every file carries the same 9 columns on every row: the market, the permit number, the issue date, the work type and trade, the source feed's own class, and where the row came from.
Maricopa County, AZ
Available12,089
permits on record, through 2026-08-09
Weekly feed available when this market clears our completeness bar.
Plus addresses on 96.4%, contractor names on 34.5%, declared values on 48.3%, ZIPs on 94.6%, measured across every row we hold.
Declared value is on 41% of recent rows.
History runs to 2026-08-09 and stops there, so that is what the file holds.
Scottsdale, AZ
Available8,470
permits on record, 3 last week
Weekly feed available when this market clears our completeness bar.
Plus addresses on 100.0%, contractor names on 70.8%, declared values on 26.5%, ZIPs on 99.8%, measured across every row we hold.
Declared value is on 28% of recent rows.
Tucson, AZ
Available7,811
permits on record, 125 last week
Plus addresses on 99.9%, contractor names on 67.2%, declared values on 46.8%, ZIPs on 99.8%, measured across every row we hold.
Mesa, AZ
Available6,972
permits on record, 97 last week
Weekly feed available when this market clears our completeness bar.
Plus addresses on 98.4%, contractor names on 48.6%, declared values on 20.6%, ZIPs on 95.1%, measured across every row we hold.
Names are on 45% for the contractor and 48% for the owner of recent rows. Declared value is on 33% of recent rows.
Tempe, AZ
Available5,154
permits on record, 12 last week
Weekly feed available when this market clears our completeness bar.
Plus addresses on 99.8%, contractor names on 2.6%, declared values on 72.6%, ZIPs on 99.8%, measured across every row we hold.
This market runs 63 permits in a recent period. Names are on 0% for the contractor and 0% for the owner of recent rows. Declared value is on 49% of recent rows.
Phoenix, AZ
Available4,964
permits on record, 0 last week
Weekly feed available when this market clears our completeness bar.
Plus addresses on 98.6%, contractor names on 0.0%, declared values on 0.0%, ZIPs on 98.5%, measured across every row we hold.
Names are on 0% for the contractor and 0% for the owner of recent rows.
Yuma, AZ
Available4,929
permits on record, through 2026-08-07
Plus addresses on 99.4%, contractor names on 87.9%, declared values on 71.2%, ZIPs on 99.3%, measured across every row we hold.
History runs to 2026-08-07 and stops there, so that is what the file holds.
Gilbert, AZ
Available4,780
permits on record, 70 last week
Weekly feed available when this market clears our completeness bar.
Plus addresses on 98.3%, contractor names on 40.6%, declared values on 24.8%, ZIPs on 98.1%, measured across every row we hold.
Declared value is on 26% of recent rows.
Peoria, AZ
Available3,167
permits on record, 37 last week
Plus addresses on 100.0%, contractor names on 88.9%, declared values on 0.0%, ZIPs on 100.0%, measured across every row we hold.
Queen Creek, AZ
Available3,036
permits on record, 49 last week
Weekly feed available when this market clears our completeness bar.
Plus addresses on 100.0%, contractor names on 0.0%, declared values on 0.0%, ZIPs on 81.2%, measured across every row we hold.
Names are on 0% for the contractor and 0% for the owner of recent rows. Declared value is on 0% of recent rows. Our own extraction is currently dropping a field this market publishes, so it is held back until that is healed.
Get a Arizona sample
Pick the markets you want to see, and we will email you real rows from them. Markets below our completeness bar can still be sampled; they are marked so you know before you look.
Every number here is computed from what we hold. See exactly what we cover.
Markets and completeness
3 of 10 markets here can be bought as a feed. The rest are sample only, and what each one is short of is on its row below.
Every figure is computed from what we actually hold. A market with no permits on record is not listed.
| Market | Permits | Recent | Availability |
|---|---|---|---|
Maricopa County, AZ
CompletenessAddress 96.4% all timeContractor 34.5% all timeDeclared value 48.3% all timeZIP 94.6% all timeData since 2025-12
|
12,089 | through 2026-08-09 | Available |
Scottsdale, AZ
CompletenessAddress 100.0% all timeContractor 70.8% all timeDeclared value 26.5% all timeZIP 99.8% all timeData since 2025-09
|
8,470 | 3 last week | Available |
Tucson, AZ
CompletenessAddress 99.9% all timeContractor 67.2% all timeDeclared value 46.8% all timeZIP 99.8% all timeData since 2025-12
|
7,811 | 125 last week | Available |
Mesa, AZ
CompletenessAddress 98.4% all timeContractor 48.6% all timeDeclared value 20.6% all timeZIP 95.1% all timeData since 2024-09
|
6,972 | 97 last week | Available |
Tempe, AZ
CompletenessAddress 99.8% all timeContractor 2.6% all timeDeclared value 72.6% all timeZIP 99.8% all timeData since 2022-12
|
5,154 | 12 last week | Available |
Phoenix, AZ
CompletenessAddress 98.6% all timeContractor not published by this feedDeclared value 0.0% all timeZIP 98.5% all timeData since 2023-05
|
4,964 | 0 last week | Available |
Yuma, AZ
CompletenessAddress 99.4% all timeContractor 87.9% all timeDeclared value 71.2% all timeZIP 99.3% all timeData since 2025-07
|
4,929 | through 2026-08-07 | Available |
Gilbert, AZ
CompletenessAddress 98.3% all timeContractor 40.6% all timeDeclared value 24.8% all timeZIP 98.1% all timeData since 2025-06
|
4,780 | 70 last week | Available |
Peoria, AZ
CompletenessAddress 100.0% all timeContractor 88.9% all timeDeclared value 0.0% all timeZIP 100.0% all timeData since 2025-06
|
3,167 | 37 last week | Available |
Queen Creek, AZ
CompletenessAddress 100.0% all timeContractor 0.0% all timeDeclared value 0.0% all timeZIP 81.2% all timeData since 2024-12
|
3,036 | 49 last week | Available |
Reference
What a feed includes, the exact columns, where the rows come from, and what we will not claim. Open what you need.
What a feed includes
A feed is the underlying permit records for the markets you name, delivered on a schedule you set, as one row per permit with the columns listed below. It is the same data behind every number on this page, without the product wrapped around it: you get the file and use it inside the terms you agree to. For Arizona that means every market listed above, or any subset of them, with the completeness shown per market rather than promised in general.
What every file includes, 18 columns
| Column | Type | What it holds |
|---|---|---|
| city_slug | text | Our stable identifier for the jurisdiction that issued the permit. |
| city_name | text | Display name of that jurisdiction. |
| permit_number | text | The issuing authority's own permit identifier, verbatim. |
| issue_date | date | Date the permit was issued, as published by the source. |
| address | text | Site address of the work, as published. |
| zip | text | Site ZIP. Published by the feed where available, otherwise derived from the address by the Census geocoder. zip_source records which. |
| latitude | text | Census geocoder latitude, present only for confident address matches. |
| longitude | text | Census geocoder longitude, present only for confident address matches. |
| permit_type | text | Work type axis: RENOVATION, REMODEL, ADDITION or REPAIR. Null when the row is a specialty trade instead. |
| trade | text | Trade axis: ROOFING, ELECTRICAL, HVAC, PLUMBING, SOLAR or POOL. Null when the row is a work type instead. |
| source_class | text | The source feed's own work class, verbatim and upper cased. The closest thing in the row to the issuing authority's own taxonomy. |
| category | text | TRADE when a specialty trade was detected, RESIDENTIAL when a work type was detected. Not a building occupancy flag. |
| declared_cost | integer | Applicant declared job value in whole dollars. An estimate supplied at application, never an actual cost. |
| contractor | text | Contractor of record, as published. |
| contractor_license | text | Contractor licence or registration number where the source publishes one. |
| owner | text | Owner of record, as published. In the files you buy only, never shown on a page, in an email, or in the dashboard. |
| ward | text | Ward or council district where the source publishes one. |
| source | text | Where the row came from: straight from the city, the city's open data, or an aggregated feed. |
Where these rows come from
Direct. We pull the issuing authority's own publication ourselves, on our own schedule. Fastest to reflect a change at the source, and the shape of the file is whatever that authority publishes.
City open data. The jurisdiction publishes its permits as an open dataset under terms that grant reuse, and we ingest it under those terms. Every one of these was read by a person before it was switched on, and the licence is recorded per city.
Aggregated feed. The records reach us through a permit data aggregator that has already gathered them from the issuing authority. Broadest reach and the most normalisation applied before we see it, which is why the source column tells you which rows came this way.
One row per permit, not one row per update. A permit that is amended, re-inspected or re-issued does not become a second record: rows are collapsed on the issuing authority's own permit number within a jurisdiction, and where two sources both describe the same permit we keep one and compare the rest. What that means for you is that a count of rows is a count of permits, so you can bill, forecast and prospect off it without deduplicating anything yourself.
The honest part
Building permits carry no phone numbers and no email addresses, so no honest permit feed includes them. How complete each field is varies by jurisdiction because publication varies by jurisdiction: some authorities publish contractor names and some do not, and where one does not you get an explicit note rather than an empty column you might mistake for a bad extraction. Every completeness figure on this page is computed from what we actually hold.
Why is a market sample only?
We only sell markets with complete data. Every figure on this page is computed from what we actually hold, and you see exactly what a market carries before you pay. Anything short of complete is sample only until it clears the bar.
Custom feeds and embedded use are quoted per deal. Email us and a person will answer.
Our coverage and field fill, every city / All permit data feeds