Building Violations — Chicago: full dataset avatar

Building Violations — Chicago: full dataset

Deprecated

Pricing

from $0.50 / 1,000 results

Go to Apify Store
Building Violations — Chicago: full dataset

Building Violations — Chicago: full dataset

Deprecated

Violations issued by the Department of Buildings from 2006 to the present. Lenders and title companies, please note: These data are historical in nature and should not. Returns 31 declared fields as flat JSON. Public Chicago Open Data data, no key.

Pricing

from $0.50 / 1,000 results

Rating

0.0

(0)

Developer

Alauddin burki

Alauddin burki

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Features

Limited permissions

Share

Violations issued by the Department of Buildings from 2006 to the present. Lenders and title companies, please note: These data are historical in nature and should not be relied upon for real estate transactions. For transactional purposes such as closings, please consult the title commitment for outstanding enforcement actions in the Circuit Court of Cook County or the Chicago Department of Administrative Hearings. This Actor returns it as one flat JSON row per record, with 31 declared fields — typed, named and documented in the dataset schema, so a spreadsheet or an agent can use it without guessing.

What you get

FieldTypeMeaning
property_groupnumberPROPERTY GROUP
street_directionstringSTREET DIRECTION
department_bureaustringDEPARTMENT BUREAU
location_citystringLOCATION (city)
violation_status_datestringVIOLATION STATUS DATE
location_statestringLOCATION (state)
location_zipstringLOCATION (zip)
ssanumberSSA
street_typestringSTREET TYPE
inspection_statusstringINSPECTION STATUS
latitudenumberLATITUDE
violation_ordinancestringVIOLATION ORDINANCE
street_namestringSTREET NAME
violation_locationstringVIOLATION LOCATION
addressstringADDRESS
inspection_waivedstringINSPECTION WAIVED
latitude_2numberLatitude
longitudenumberLongitude
location_addressstringLOCATION (address)
violation_last_modified_datestringVIOLATION LAST MODIFIED DATE

The output schema lists all 31 fields; the table above is the first twenty.

Every row also carries sourceRowId, sourceUpdatedAt and scrapedAt, so a pipeline can tell one record from another and know exactly when it was read.

{
"property_group": 24647,
"street_direction": "S",
"department_bureau": "CONSERVATION",
"location_city": "text",
"violation_status_date": "text",
"location_state": "text",
"location_zip": "text",
"ssa": 42
}

Inputs

FieldWhat it does
Filter (SoQL)Applied at the source, so a narrow question fetches a narrow page instead of downloading everything.
OrderEmpty keeps the publisher's own order; set a column to sort, for example amount DESC.
Maximum rowsHard cap. The source is paged 1,000 rows at a time.
Time budgetStops cleanly and reports how far it got.
Pause between pagesKeeps the run inside the publisher's rate limits.

Limitations

  • This is one dataset, from one publisher. It is the Building Violations dataset as City of Chicago publishes it — not a national or cross-city equivalent, and not a merge with other sources.
  • The publisher can change it. Columns are added, renamed and retired upstream; the field list here is the schema the Actor was generated from. A renamed column arrives as a new field only after the Actor is updated.
  • Fields are typed from live records. A column that was empty in the sample is declared as text; a value that does not fit the declared type comes back null rather than being coerced into a wrong number.
  • Records are what the publisher publishes. No geocoding, no de-duplication across datasets, no enrichment.
  • Freshness is the publisher's. The data was last changed upstream on 2026-10-25. Where the publisher supplies a row timestamp it appears as sourceUpdatedAt; scrapedAt records when this Actor read the row.

Why this is different

  • Building Violations — Chicago: full dataset declares all 31 of its output fields in the dataset schema, each with a type, a description and an example.
  • The Actor reads the Building Violations dataset directly from Chicago Open Data; no key, login or account is needed.
  • Filters run at the source with SoQL, so a narrow request returns a narrow page rather than a full download.
  • Every row is flat JSON: nested location objects become latitude and longitude, and no field holds a nested object.
  • The row id is stable, so the same request de-duplicates instead of returning the same record twice.

FAQ

Do I need an API key? No. Chicago Open Data publishes this dataset openly.

How fresh is it? The Actor reads the dataset live. scrapedAt records when each row was read, and sourceUpdatedAt carries the publisher's own row timestamp where it supplies one.

Can I filter by date or status? Yes — use the Filter field with SoQL, for example status = 'Active'.

What happens if my filter is wrong? The run stops with the portal's own message and the hint to check SoQL, rather than returning an empty dataset that looks like "no data".

Is this the whole dataset? Up to your row cap, paged 1,000 at a time. Raise the cap to read more.

What is sourceRowId? The publisher's own row id when it supplies one, otherwise a stable hash of the row. Either way it is what makes de-duplication and joins possible.

Pricing

Pay per result: $0.0005 per row. Each stored dataset row is billed, including any diagnostic row returned instead of results.

An Actor-start event is also charged at $0.0001 per GB of allocated memory (minimum one event), even if no rows are returned. At 1 GB or less, 1,000 result rows cost $0.5001 before any applicable Store discount.

Data source

Chicago Open Data — Building Violations, published by City of Chicago. Public data under the portal's open-data terms.