Municipal Code-Enforcement Violations — Chicago avatar

Municipal Code-Enforcement Violations — Chicago

Pricing

from $20.00 / 1,000 results

Go to Apify Store
Municipal Code-Enforcement Violations — Chicago

Municipal Code-Enforcement Violations — Chicago

Fetch public City of Chicago building-code violation records from the official Socrata dataset into structured JSON records with canonical detail URLs. Related Actor: [Foreclosure auctions](https://apify.com/slate_spool/foreclosure-auction-listings)

Pricing

from $20.00 / 1,000 results

Rating

0.0

(0)

Developer

Wes Shields

Wes Shields

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

An Apify Actor that returns structured City of Chicago building-code violation records from the City's public Socrata dataset. Phase 1 is staged locally only; it has not been pushed, deployed, or published.

Reliability and safety

  • Official public source: https://data.cityofchicago.org/resource/22u3-xenr.json
  • Canonical detail URL: https://data.cityofchicago.org/resource/22u3-xenr/{recordId}.json, constructed only from the validated numeric record ID
  • Minimum one-second request interval, matching the source robots.txt crawl delay
  • Hard caps on records (1000), attempts (50), retries (3), per-request time (30s), runtime (300s), and Actor memory (512 MB)
  • Explicit RUN_STATUS document on success or failure; partial cap exhaustion fails instead of silently succeeding
  • Pay-per-event violation-record metering when configured on Apify; otherwise explicit record/request counters accompany normal platform usage metering

The data is informational and historical. It must not be treated as a title, closing, legal, or current-condition determination.

Local validation

npm ci
npm test
npm run validate
npm run key:build
npm run score
apify actor:run

The independent key builder uses the official CSV representation and Python's CSV parser. The Actor/scorer uses the JSON representation and the production JavaScript mapper, so the two paths do not share parsing or mapping code.

No credentials are required. Do not add an Apify token for local tests and do not run apify push during the supervised build phase.