# Building Code Violations Data: Open Cases by Address (`buildingsignal/building-code-violations-data`) Actor

Building code violations and enforcement cases for Chicago, Cincinnati, Los Angeles and New York City: violation or case type, status, dates, description, address and coordinates. Export to JSON, CSV or Excel.

- **URL**: https://apify.com/buildingsignal/building-code-violations-data.md
- **Developed by:** [BuildingSignal](https://apify.com/buildingsignal) (community)
- **Categories:** Real estate, Lead generation, Business
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $15.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

[![Building Code Violations Data: Open Cases by Address](https://scrapers.lat/banners/building-code-violations-data.png)](https://console.apify.com/actors/b5J4sPE4gW58N0sUW/input)

## Building Code Violations Data: Open Cases by Address

**Building code violations by address** from Chicago, Cincinnati, Los Angeles and New York City in one schema. Rows show violation code, description and status, so you can find open problems at a property across four large cities.

Here is one real record from this actor.

```json
{
  "buildingSignalId": "5b0f198269ae2499",
  "jurisdiction": "Chicago, IL",
  "programName": "Chicago Building Violations",
  "recordType": "building_violation",
  "violationId": "7562517",
  "violationDate": "2026-10-29",
  "violationCode": "EV1110",
  "violationStatus": "OPEN",
  "violationDescription": "MAINTAIN OR REPAIR ELECT ELEVA",
  "ordinance": "Failed to maintain electric elevator equipment provided at premises in safe and sound working condition. (13-196-590, 13-196-630(b), 18-30-001)",
  "inspectionStatus": "FAILED",
  "inspectionCategory": "PERIODIC",
  "department": "Elevator",
  "inspectionNumber": "14390098",
  "addressStreet": "839 W Sheridan Rd",
  "city": "Chicago",
  "state": "IL",
  "latitude": 41.9526146743,
  "longitude": -87.6511952798,
  "country": "US",
  "source": "City of Chicago Department of Buildings",
  "observedAt": "2026-11-02T20:06:53.178Z"
}
```

**[Input](https://apify.com/buildingsignal/building-code-violations-data/input-schema) | [Output](https://apify.com/buildingsignal/building-code-violations-data/output-schema) | [Pricing](https://apify.com/buildingsignal/building-code-violations-data/pricing)**

![Coverage](https://img.shields.io/badge/Coverage-Chicago%2C%20Cincinnati%2C%20Los%20Angeles%20and%20New%20York%20City-blue)
![Output](https://img.shields.io/badge/Output-JSON%20%7C%20CSV%20%7C%20Excel-orange)
![Billing](https://img.shields.io/badge/Billing-Pay%20per%20result-brightgreen)

### Table of contents

- [What you get](#what-you-get)
- [Input and filters](#input-and-filters)
- [Use cases](#use-cases)
- [Coverage and freshness](#coverage-and-freshness)
- [Pricing](#pricing)
- [Comparison with other Apify actors](#comparison-with-other-apify-actors)
- [Related BuildingSignal actors](#related-buildingsignal-actors)
- [FAQ](#faq)
- [Run it through the Apify API](#run-it-through-the-apify-api)

### What you get

Each record can carry these 43 fields. A field the source does not publish for a record comes back as `null`.

| Field | Type | Description |
|---|---|---|
| `buildingSignalId` | string | Stable BuildingSignal building ID (same building across years and runs) |
| `jurisdiction` | string | City, county, state or province of the program |
| `programName` | string | Name of the disclosure or compliance program |
| `recordType` | string | Type of record |
| `violationId` | string | Violation ID |
| `violationDate` | string | Violation date |
| `violationCode` | string | Violation code |
| `violationStatus` | string | Violation status |
| `violationDescription` | string | Violation description |
| `ordinance` | string | Ordinance text |
| `inspectionStatus` | string | Inspection status |
| `inspectionCategory` | string | Inspection or certificate category |
| `department` | string | Department / bureau |
| `inspectionNumber` | string | Inspection number |
| `addressStreet` | string | Street address |
| `city` | string | City |
| `state` | string | State or province |
| `latitude` | number | Latitude |
| `longitude` | number | Longitude |
| `country` | string | Country code (US or CA) |
| `source` | string | Official source program or agency |
| `observedAt` | string | When this record was collected (ISO timestamp) |
| `caseNumber` | string | Case number |
| `caseDate` | string | Case opened date |
| `caseType` | string | Case type |
| `caseSubtype` | string | Case subtype |
| `agency` | string | Agency |
| `status` | string | Status |
| `open` | boolean | True while the case is open |
| `lastUpdated` | string | Last updated |
| `neighborhood` | string | Neighborhood |
| `area` | string | Area office |
| `zip` | string | ZIP or postal code |
| `parcelId` | string | Tax parcel / lot identifier (BBL, SSL, APN, folio, etc.) |
| `violationNumber` | string | Violation number |
| `violationType` | string | Violation type |
| `remarks` | string | Violation remarks |
| `deviceType` | string | Device type |
| `deviceNumber` | string | Device number |
| `cycleEndDate` | string | Inspection cycle end date |
| `borough` | string | NYC borough |
| `bin` | string | NYC Building Identification Number (BIN) |
| `bbl` | string | NYC Borough-Block-Lot tax lot ID |

### Input and filters

All inputs are optional.

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `sources` | array | no | (none) | Which sources to include. Leave empty for all. Values: `chicago_violations`, `cincy_code`, `la_code`, `nyc_safety_violations`. |
| `sinceDate` | string | no | (none) | Only records issued or opened on or after this date. Leave empty for all. |
| `statusContains` | array | no | (none) | Keep records whose status contains any of these words, e.g. Active, Open, Unsafe, Expired. |
| `categoryContains` | array | no | (none) | Keep records whose type or category contains any of these words. |
| `zipCodes` | array | no | (none) | Only records in these ZIP or postal codes (where published). |
| `keyword` | string | no | (none) | Only records containing this text anywhere (address, name, type, description...). |
| `maxRecords` | integer | no | `50` | Maximum number of violations to return. Free Apify plans are limited to 10 per run. |

A working example to paste into the Input tab:

```json
{
  "sinceDate": "2026-10-01",
  "maxRecords": 25
}
```

### Use cases

- Flag open violations during property due diligence in any of the four cities.
- Find properties with elevator, electrical or structural violations for licensed trades.
- Compare enforcement activity across cities by violation type.

### Coverage and freshness

Program: Chicago Building Violations. Publisher: City of Chicago Department of Buildings. Area in this example record: Chicago, IL. Each run reads the current official publication, so a scheduled run picks up new releases when the agency publishes them. Fields the program does not publish come back as null.

### Pricing

This actor uses pay-per-event pricing. These are the current Apify prices, read on 2026-11-06.

| Event | Price | When it is charged |
|---|---|---|
| `result` | $0.015 | Each violation delivered to your dataset |
| `apify-actor-start` | $0.003 | When a run starts, once per GB of run memory with a minimum of one |

At the default 512 MB, a run that delivers 100 violations costs $1.503.

- Accounts on the free Apify plan receive up to 10 results per run.
- If nothing matches your filters, no results are charged. If the source cannot be read before any result is saved, you get one row with an `error` field, and that row carries no `result` charge. The start event still applies to the run.
- Set a maximum cost per run and the actor stops delivering results when it reaches that limit.

### Comparison with other Apify actors

Other developers list actors that cover this source or part of it. This coverage comes from the public Apify Store listings on 2026-11-06 and can change.

| Actor | What the listing covers |
|---|---|
| **This actor** | Building Code Violations Data |
| `permitdata/us-code-violations-scraper` | City code violations from 15 sources, naming Chicago and NYC |
| `radiant_opuntia/code-violations-alerts` | Violation alerts naming NYC, Chicago and Cincinnati |
| `datapenguin/code-violation-leads` | Code violations from 11 places, naming NYC, LA, Chicago and Cincinnati |
| `gazidev/code-violation-leads` | Code violations naming NYC, Chicago and Los Angeles |

This actor returns the 43 output fields listed above. We did not run the other actors, so this table makes no claim about their output, speed or reliability. Other listings that also name this source: `j0401/us-code-violations`, `maniginam/city-building-permits-code-violations`, `nerolabs/code-violation-leads`.

### Related BuildingSignal actors

Other public BuildingSignal actors for the same buyer:

- [Vacant Building Registry Data: Vacant & Abandoned Properties](https://apify.com/buildingsignal/vacant-building-registry-data): code and vacancy records
- [Certificates of Occupancy Feed: Newly Completed Buildings](https://apify.com/buildingsignal/certificates-of-occupancy-feed): certificates of occupancy
- [Allentown PA Rental Licenses: Licensed Rental Units & Parcels](https://apify.com/buildingsignal/allentown-rental-licenses): rental registry data
- [Baton Rouge Fire Inspections: Inspected Businesses & Sites](https://apify.com/buildingsignal/baton-rouge-fire-inspections): building safety records

### FAQ

**Where does the data come from?**

From official public records and open-data disclosures published by the government programs named on this page. BuildingSignal standardizes them into one consistent schema. Always confirm critical decisions with the issuing agency.

**Can I use it with my CRM or BI tool?**

Yes. Export to CSV, Excel or JSON, call it through the Apify API, or connect it with the Make, Zapier, n8n or Google Sheets integrations.

**What can I filter by?**

The input accepts `sources`, `sinceDate`, `statusContains`, `categoryContains`, `zipCodes` and `keyword`. The Input and filters section explains each one.

**Can I run it on a schedule?**

Yes. Create an Apify schedule for the actor, then send the dataset to your database, a spreadsheet or a webhook.

### Run it through the Apify API

Replace `<TOKEN>` with your Apify API token.

```bash
curl -X POST "https://api.apify.com/v2/acts/buildingsignal~building-code-violations-data/run-sync-get-dataset-items?token=<TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"sinceDate": "2026-10-01", "maxRecords": 25}'
```

With the Apify CLI:

```bash
apify call buildingsignal/building-code-violations-data --input '{"sinceDate": "2026-10-01", "maxRecords": 25}'
```

Every run writes to a dataset that you can export as JSON, CSV or Excel from the Storage tab or through the Apify API.

***

*BuildingSignal is an independent data provider and is not affiliated with, endorsed by or sponsored by any government agency or program named on this page. Data comes from official public records; always confirm critical decisions with the issuing agency.*

# Actor input Schema

## `sources` (type: `array`):

Which sources to include. Leave empty for all.

## `sinceDate` (type: `string`):

Only records issued or opened on or after this date. Leave empty for all.

## `statusContains` (type: `array`):

Keep records whose status contains any of these words, e.g. Active, Open, Unsafe, Expired.

## `categoryContains` (type: `array`):

Keep records whose type or category contains any of these words.

## `zipCodes` (type: `array`):

Only records in these ZIP or postal codes (where published).

## `keyword` (type: `string`):

Only records containing this text anywhere (address, name, type, description...).

## `maxRecords` (type: `integer`):

Maximum number of violations to return. Free Apify plans are limited to 10 per run.

## Actor input object example

```json
{
  "sinceDate": "2026-10-01",
  "maxRecords": 50
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "sinceDate": "2026-10-01",
    "maxRecords": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("buildingsignal/building-code-violations-data").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "sinceDate": "2026-10-01",
    "maxRecords": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("buildingsignal/building-code-violations-data").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "sinceDate": "2026-10-01",
  "maxRecords": 50
}' |
apify call buildingsignal/building-code-violations-data --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,buildingsignal/building-code-violations-data"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/b5J4sPE4gW58N0sUW/builds/wTaNGEqhetDHTqSBB/openapi.json