New Jersey Statewide Construction Permits

New Jersey's construction-permit register is statewide - every municipality in the state files into one system (PermitsNJ) and the state publishes the whole thing as open data. This actor turns that single table into a charged-per-record lookup, filter and aggregate tool: pull a county or a town, range-filter by construction cost or fee, read one parcel by block and lot, or aggregate the state by county, permit type or building use.

Built for: contractors and suppliers sizing a market, developers and GCs reading a pipeline, and anyone doing property or construction diligence who wants the whole state in one query instead of stitching together two dozen municipal portals.

What it covers

2,678,321 permits and certificates - the state's full file, across 22 counties and 549 municipalities. Each row is a permit (1,366,473) or the certificate that closes it (1,311,848) - the same permit number carries both ends of the job.

Depth beyond a bare permit list:

• the full code fee breakdown - building, plumbing, electrical, fire, DCA, certificate, elevator and other fees, summed into totalfee (2,606,015 rows carry a fee)
• the reported construction cost (2,604,765 rows), cubic volume, floor area (149,991 rows carry a non-zero square footage - the column is present on every row but zero on the rest) and rent / sale gained
• the use group with its ICC description - R-5 (1,900,875), R-3, R-2, B, M, A-2, E, U, ... - and every type code paired with its word (Alteration 2,389,866 / New 112,293 / Demolition 111,086 / Addition 65,076)
• the local parcel key: municipality + block + lot + county, plus the certificate type and the state's processing date.

The fine print that matters

Two source quirks are handled for you. Impossible future dates - the register holds permit dates out to year 2925 and certificate dates to 6013 - are excluded from every query and blanked on output, so a newest-first pull can never surface a year-2925 row. And the source updates roughly monthly (the state's own processing date, and the register's update stamp, advance on the order of weeks), so there is no per-row change marker on this dataset; the recency axis is the permit date itself, and 227,886 permits carry a valid 2026 date.

The number that sells it: this is a 2.68M-row statewide table, not a city portal. A New permit over $1M in Bergen County, every alteration in Toms River, one parcel's full permit history by block and lot - all in one query, and aggregate by county, municipality, permit type or building use across the whole state.

Typical questions

• "Every new-construction permit over $1M in Bergen County."
• "Permits in Toms River / Edison / Hamilton."
• "One parcel's full permit history by block + lot."
• "The fee breakdown and reported cost on a permit number."
• "Aggregate the state by county, permit type or building use group."

Inputs

Input	What it does
mode	rows (default) / aggregate
status / permitType / useGroup	permit vs certificate; alteration / new / addition / demolition; ICC use group
certificateType	certificate type
county / municipality	where (22 counties, 549 municipalities)
permitNumber	exact permit number
block / lot	local parcel key
constCostMin/Max / totalFeeMin/Max / squareFeetMin/Max	cost, fee and floor-area ranges
issuedFrom/To / processedFrom/To	permit-date and processing-date ranges
groupBy	aggregate over county / municipality / status / permit type / use group / certificate type
maxResults	cap records (default 200)

Default run = the 200 most recent permits - fast for the daily auto-test. For a targeted query add a filter; for a broad view use aggregate.

Low cost

From $0.0001 per record - billed only for the rows you use, at the platform floor. Cost scales with what you pull, not with the size of the register, and because each record is metered individually there's no per-run charge cap to hit on a big pull.

What a thin scraper misses is the two ends of a job living in the same table: every certificate row is a permit's sign-off, filed under the same permit number months or years later, so "which permits were actually closed" is a join a naive pull never makes. The registers also carry impossible dates out to year 2925 and 6013 - dump them newest-first and the top of your result is garbage - and the numeric columns arrive as strings over the wire even though the state compares them as numbers, so a text-ordered cost column sorts $9 above $100,000. Normalizing permit-and-certificate, the runaway dates and the string-numbers into a schema where a county / constCostMin / permitType query returns exactly the jobs you mean is the actual product. Every pull is integrity-checked against the register's known shape, so a degraded source fails loudly instead of returning bad rows.

Source

• New Jersey: Construction Permit Data - the statewide permit register every NJ municipality files into. Public open data. Records are the state's own published fields; not an endorsement of any contractor or property.