How PermitStream.dev works
A high-level look at how permit data flows from city open-data portals into the API.
City open-data portals
Each covered city (Austin TX, Chicago IL, Calgary AB) already publishes permit filings on its own public open-data portal.
Daily ingestion
A scheduled job delta-syncs new and updated permits from each portal once a day, scrubbing any private-individual names before anything is stored.
Normalized database
Every permit lands in one consistent schema, regardless of which city or source system it came from.
PermitStream.dev API
A single JSON API serves normalized permit records to authenticated callers, with per-tier rate limits and pagination.
Your application
Query permits with a Bearer API key — build lead lists, monitoring dashboards, or automated alerts on top of the response.
API Docs
docs.permitstream.dev renders the live OpenAPI schema straight from the API, so the reference never drifts out of date.