Chicago Building Violations Scraper
Pricing
from $11.99 / 1,000 result items
Chicago Building Violations Scraper
Scrapes Chicago building violations by ward, violation code, case disposition, or date range. Returns each violation as a flat row with case details, status, and location.
Pricing
from $11.99 / 1,000 result items
Rating
5.0
(1)
Developer
ParseForge
Maintained by CommunityActor stats
1
Bookmarked
2
Total users
0
Monthly active users
7 days ago
Last modified
Categories
Share
Chicago Building Violations Scraper
Scrape Chicago building violations by ward, code, disposition, or date range. Each violation comes with its case details, status, and location. No login or API key. Export to CSV, JSON, Excel, or XML.
Chicago's building violations data is public but scattered across a clunky portal. This Actor reads the city's violation records directly, filtered by ward, violation code, disposition, or date range, and returns each match in one fixed schema.
| Who uses it | What they scrape Chicago Building Violations for |
|---|---|
| Real estate investors | Find distressed properties with open violations before they hit the market |
| Property managers | Monitor violation histories for buildings they manage or plan to acquire |
| Journalists | Investigate patterns of building code enforcement across neighborhoods |
| Urban planners | Analyze violation density by ward to identify areas needing intervention |
| Insurance underwriters | Assess property risk based on violation frequency and severity |
What it does
This Actor collects Chicago building violations by ward, violation code, case disposition, or date range, and returns each one as a flat row.
- π Ward filter: narrow results to a specific Chicago ward (1-50)
- π’ Violation code filter: target a specific code like '190019'
- βοΈ Disposition filter: select Liable, Not Liable, Default, or other statuses
- π Date range: set start and end dates for violation dates
- π’ Max items: control how many violations to collect per run
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with Chicago Building Violations data
π Find distressed properties.
A real estate investor runs the Actor for a specific ward and date range to identify buildings with recent violations, then cross-references with property listings to find motivated sellers.
π Track enforcement trends.
A journalist scrapes violations by disposition and ward over several months to reveal which neighborhoods receive more citations and how cases are resolved.
π’ Assess portfolio risk.
An insurance underwriter pulls violation histories for all properties in a portfolio to adjust premiums based on code compliance.
πΊοΈ Map violation hotspots.
An urban planner collects violations by ward and date range to create heat maps showing where building safety issues concentrate.
Why choose this scraper
| What you get | |
|---|---|
| No login or API key | Access public violation data without registration |
| Flexible filters | Combine ward, code, disposition, and date range |
| Structured output | Each violation as a flat row ready for analysis |
| Export options | CSV, JSON, Excel, or XML for any workflow |
How it compares
No other Store actor targets Chicago Building Violations the same way, so the honest comparison is with the alternatives teams actually weigh.
| Chicago Building Violations Scraper | Build it in-house | By hand | |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When Chicago Building Violations changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |
Configure the run
Drive the Actor from ward, violation code, case disposition, and date range, alone or together, and filters run as each violation is read so only matches reach your dataset. The Input tab lists every parameter.
A first run with the defaults:
{"maxItems": 10}
A larger pull:
{"maxItems": 200}
Pricing
Pay-per-result: $0.01599 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $1.60 |
| 1,000 results | $15.99 |
| 10,000 results | $159.90 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the Chicago Building Violations Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to Chicago Building Violations through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/chicago-building-violations-scraper"
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Check your filters. If you set a ward, violation code, disposition, or date range that has no matching violations, the Actor returns an empty dataset. Try broadening the date range or removing some filters.
The Actor is taking too long.
Reduce the 'Maximum violations' input. The Actor stops after collecting that many records, so a lower number finishes faster.
I got an error about the ward number.
Ward must be an integer between 1 and 50. Check that you entered a valid number.
The date format is not working.
Use YYYY-MM-DD format, for example 2025-01-01. Do not use slashes or other separators.
FAQ
| Question | Answer |
|---|---|
| What data does this Actor return? | It returns Chicago building violations with case details, status, and location. The exact fields are shown in the sample output. |
| Do I need an API key or login? | No. The Actor reads public violation data directly from the City of Chicago's portal. |
| Can I filter by multiple wards? | The input accepts a single ward number. To get multiple wards, run the Actor multiple times or use a separate integration. |
| What date format should I use? | Use YYYY-MM-DD, for example 2025-01-01. |
| How many violations can I collect? | Set the 'Maximum violations' input to any number from 1 upward. The default is 10. |
| What is a violation code? | A code like '190019' that identifies the specific building code section violated. |
| What does 'case disposition' mean? | The outcome of the case, such as Liable, Not Liable, or Default. |
| Can I export the data? | Yes, you can export to CSV, JSON, Excel, or XML from the Apify dataset. |
| Is this data updated in real time? | The Actor scrapes the current public records each time it runs, so you get the latest available data. |
| Can I schedule this Actor to run regularly? | Yes, you can set up a schedule in Apify to run it daily, weekly, or at any interval. |
Related actors
Browse the full ParseForge collection for more scrapers.
π Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
β οΈ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by City of Chicago. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
