Building Permit API - Permits, Contractors, Property Data

contractor-record

Charged once for each contractor: legal and business name, any trading name, licence number with its issue and expiry dates, the trade classifications derived from the firm's actual work, business phone, email and website, LinkedIn profile, SIC and NAICS codes, revenue and employee count bands, review count and rating, and the permit history behind it all, meaning permit count, average and total job value, average construction duration and average inspection pass rate. Priced above a permit row because one row summarises a firm's whole record.

property-record

Charged once for each property: parcel number, property type and detail, legal owner and owner type, year built, lot size, building area, storey and unit counts, assessed market value, coordinates, and the permit history summarised on the one record, meaning permit count, contractor count, total job value, every work tag seen, the statuses present and the last permit date by tag and by status. Locations with no property on record are not charged.

decision-record

Charged once for each zoning or land use decision: its title, date, description and the provider's note on why it matters, the asset class, category and subcategory, the previous and new zoning with the uses the change allows, the project value and lot size, the applicant, owner, representative and developer named on it, the address and coordinates, and the source URL for the underlying record.

metric-record

Charged once for each metric row: for one place or one contractor, one work tag and one month, the permit count, active and in-review counts, contractor count, average and total job value, average approval and construction durations and average inspection pass rate. Priced well below a record row because a metric is an aggregate over many of them and is how you size a market before collecting it.

reference-record

Charged once for each geography lookup result, geography detail, covered ZIP code, permit tag, data coverage row, release date and credit usage row. This is how you turn a place name into the geo_id every other search needs, and how you check what a jurisdiction actually publishes before spending anything on it, so it is priced near zero.