Permit Status Tracker — Track Building Permits Across Cities
Pricing
from $5.00 / 1,000 results
Permit Status Tracker — Track Building Permits Across Cities
Stop refreshing city portals. Track your building permits by number across major US cities — daily status rows, change flags, official data. No logins. Pay per check.
Pricing
from $5.00 / 1,000 results
Rating
0.0
(0)
Developer
Salim
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
7 days ago
Last modified
Categories
Share
Stop refreshing city portals. Track your building permits by number across major US cities — daily status rows, change flags, official data. No logins. Pay per check.
What it does
Give it a list of permit numbers with their cities. Each run returns one row per permit with the current status, whether it changed since last time, and key details like address, permit type, and issue date. Schedule it daily and get an alert when anything moves.
First run: every permit gets first_check: true and previous_status: null — this is your baseline.
Second run: each permit gets first_check: false, status_changed: false (if nothing moved), and previous_status filled from the prior run.
changesOnly: true: only emits rows where the status actually changed. A run with no changes costs $0.
Cities
| Key | City | Status |
|---|---|---|
austin | Austin, TX | ✅ Live |
sf | San Francisco, CA | ✅ Live |
chicago | Chicago, IL | Coming soon |
nyc | New York, NY | Coming soon |
los_angeles | Los Angeles, CA | Coming soon |
seattle | Seattle, WA | Coming soon |
Coverage expands by request — open an issue.
Input
{"permits": [{ "city": "austin", "permitNumber": "2024-123456" },{ "city": "sf", "permitNumber": "202401234567" }],"changesOnly": false}
| Field | Type | Default | Description |
|---|---|---|---|
permits | array | required | Each item: {city, permitNumber}. City must match a key from the table above. |
changesOnly | boolean | false | Only emit rows where status changed. Runs with no changes cost $0. |
resetState | boolean | false | Wipe all tracked state and re-baseline on next run. |
appToken | string | — | Optional Socrata app token for higher rate limits. |
Output fields
| Field | Description |
|---|---|
permit_number | Permit number as provided |
city | City label (e.g., "Austin, TX") |
city_key | City key (e.g., "austin") |
found | false if the permit wasn't found in the dataset |
status | Current permit status |
previous_status | Status from the prior run (null on first check) |
status_changed | true if status differs from last run |
first_check | true on the very first run for this permit |
address | Permit site address |
permit_type | Permit type / work class |
issued_date | Issue date (ISO string) |
zip | ZIP code |
latitude / longitude | Coordinates |
description | Work description |
checked_at | ISO timestamp of this run |
Sample output
| permit_number | city | status | previous_status | status_changed | first_check | address |
|---|---|---|---|---|---|---|
| 2026-070339 PP | Austin, TX | Active | null | false | true | 9305 BREEZE HILL DR |
| 201806293452 | San Francisco, CA | expired | null | false | true | 930 Sutter St |
| 2026-070339 PP | Austin, TX | Active | Active | false | false | 9305 BREEZE HILL DR |
Billing
$5.00 per 1,000 results ($0.005 per status row) — billed via Apify's automatic per-dataset-item event. No double-billing. A changesOnly run that emits zero rows costs $0.
Schedule it
Set a daily schedule with your permit list and changesOnly: true for a zero-cost daily watch that only charges you when a status actually changes.
Data sources
- Austin: Issued Construction Permits — Austin Open Data
- San Francisco: Building Permits — DataSF / DBI (updated nightly)
See also
US Building Permits — daily feed of new permits across cities, for lead generation and construction analytics.