# Municipal Code-Enforcement Violations — Chicago (`slate_spool/municipal-code-enforcement-violations`) Actor

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)

- **URL**: https://apify.com/slate\_spool/municipal-code-enforcement-violations.md
- **Developed by:** [Wes Shields](https://apify.com/slate_spool) (community)
- **Categories:** Real estate, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.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

## Municipal Code-Enforcement Violations — Chicago

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

```sh
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.

### Related Actor

- [Foreclosure Auction Listings](https://apify.com/slate_spool/foreclosure-auction-listings) — Continue your workflow with this related data source.

# Actor input Schema

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

Hard result cap for this run (1–1000).

## `violationIds` (type: `array`):

Optional exact numeric City violation IDs. At most 100.

## `startDate` (type: `string`):

Optional inclusive violation date in YYYY-MM-DD format.

## `endDate` (type: `string`):

Optional inclusive violation date in YYYY-MM-DD format.

## `status` (type: `string`):

Return all statuses or one official status.

## `violationCodes` (type: `array`):

Optional exact code list, for example CN061014 or EV1110. At most 50.

## `addressContains` (type: `string`):

Optional case-insensitive text contained in the municipal address.

## `pageSize` (type: `integer`):

Rows requested per official API call (1–1000).

## `maxRequests` (type: `integer`):

Hard network-attempt cap, including retries (1–50).

## `requestDelayMillis` (type: `integer`):

Polite delay; cannot be lower than the source robots.txt crawl-delay of one second.

## `requestTimeoutSeconds` (type: `integer`):

Per-attempt timeout (5–30 seconds).

## `maxRetries` (type: `integer`):

Retries for timeouts, HTTP 429, and server errors (0–3).

## `maxRunSeconds` (type: `integer`):

Actor-side wall-clock safety cap (15–300 seconds).

## Actor input object example

```json
{
  "maxRecords": 100,
  "violationIds": [],
  "startDate": "",
  "endDate": "",
  "status": "ANY",
  "violationCodes": [],
  "addressContains": "",
  "pageSize": 100,
  "maxRequests": 10,
  "requestDelayMillis": 1100,
  "requestTimeoutSeconds": 20,
  "maxRetries": 2,
  "maxRunSeconds": 120
}
```

# Actor output Schema

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

Canonical structured records in the default dataset.

## `runStatus` (type: `string`):

Success/failure, counts, caps, and source metadata; prevents silent empty or partial runs.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("slate_spool/municipal-code-enforcement-violations").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("slate_spool/municipal-code-enforcement-violations").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 '{}' |
apify call slate_spool/municipal-code-enforcement-violations --silent --output-dataset

```

## MCP server setup

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

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/DsiklV3oFRqM3jLrq/builds/2FKVSxKYGoVdDwhfN/openapi.json