# Building & Housing Violations Scraper: Code Enforcement Alerts (`radiant_opuntia/code-violations-alerts`) Actor

New building, housing and code enforcement violations from 13 US cities: NYC (HPD, DOB, ECB, NYCHA, LL97, elevators), LA, Chicago, Philadelphia, SF, Seattle, Austin, New Orleans, Orlando, Norfolk, Cincinnati, Montgomery MD, Reading PA. Owner names, fines, ZIP filter. Distressed-property leads.

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

## Pricing

$3.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

**Get new building, housing and property code violations and code enforcement cases from 13 US cities and counties in one format, with address, status, violation text and case number. Built for distressed-property leads, portfolio monitoring and risk checks.**

**Rate your experience:** if you have used this Actor, you can tell us how it went on the [reviews page](https://apify.com/radiant_opuntia/code-violations-alerts/reviews). Honest feedback of any kind helps us improve it.

### What it does and who it is for

This Actor reads the **official open-data portals** of **New York City (HPD housing violations, DOB building violations, DOB safety violations: elevators, Local Law 97 emissions filings, facades, and NYCHA public housing violations by development), Los Angeles (LADBS code enforcement cases), Chicago (building violations, plus building code hearings with the named respondent, fine and upcoming hearing date), Philadelphia (L\&I violations, with owner of record), San Francisco (DBI notices of violation), Seattle, Austin, New Orleans, Orlando FL, Norfolk VA, Cincinnati, Montgomery County MD (housing code) and Reading PA (code enforcement citations)** and returns one flat record per violation, notice item or complaint: **address, ZIP, latitude and longitude, date opened, status (open, closed, other), severity (NYC hazard class, Austin priority), violation code, category, the violation text, and a case or notice number**.

Filter by city, keyword in the violation text, address, ZIP, violation versus complaint, open only and date window. Turn on **Only new** for a daily lead feed.

#### Use cases

- **Real-estate investors and wholesalers (distressed-property leads):** pull open violations such as unsafe structures, vacant buildings, overgrown lots and failed repairs, then match them to your list or skip-trace them. Example: `{"jurisdictions": ["philadelphia"], "openOnly": true, "keyword": "unsafe", "onlyNew": true}` gives a daily feed of newly cited unsafe Philadelphia buildings, with the owner of record.
- **Landlords:** get told the day the city cites one of your addresses, before fines or a court date pile up. Example: `{"address": "1425 fitzwater", "openedWithinDays": 30}`.
- **Property managers:** watch every building in a portfolio by ZIP or street, and send new violations to Slack, email or a sheet on a daily schedule.
- **Insurers, lenders and title companies:** check an address or ZIP for recent or open enforcement before you underwrite, lend or close, and monitor what is already on the books.
- **Contractors, roofers, pest-control and remediation companies:** reach owners who were just cited for roof, mold, pest or plumbing problems.
- **Tenant advocates, journalists and researchers:** track hazardous housing conditions by ZIP.
- **AI agents:** answer "any new open violations on Broadway in ZIP 10452 this week?".

### Why use this instead of the free official site or API

The underlying data is public and the official sources are free. What this Actor adds is convenience: 13 different city and county feeds become one format.

| What you need | Official site / API | This Actor |
|---|---|---|
| Covering several cities | Each city has its own portal, columns and statuses | One input and one record format |
| Comparing status and severity | Different wording in each city | A normalized `status` (open, closed, other) plus the city's own wording in `statusText`; severity where the city publishes it |
| Violations vs complaints | Mixed in different datasets | `recordType` is violation or complaint, with a filter |
| Narrowing a huge feed | Write a filter query for each portal | Keyword, address, ZIP, open-only and date filters across all cities |
| Only new records | Compare exports yourself | **Only new** mode with a named alert |

If you only need a single lookup now and then, the official site is fine. If you want the same data on a schedule, as flat rows you can feed to a spreadsheet, CRM or agent, this saves the glue work.

### Data fields

| Field | Type | What it contains |
|---|---|---|
| `jurisdiction` | text | Name of the city feed. |
| `jurisdictionCode` | text | nyc, nyc_dob, nyc_dob_safety, nyc_nycha, nyc_oath_dob, los_angeles, chicago, chicago_hearings, philadelphia, sf, seattle, austin, new_orleans, orlando, norfolk_va, cincinnati, montgomery_md or reading_pa. |
| `recordId` | text | Record ID from the source. |
| `recordType` | text | violation (cited violation or notice) or complaint (a complaint or service request that may lead to one). |
| `openedDate` | date | Date the violation or complaint was opened. |
| `status` | text | Normalized status: open, closed or other. |
| `statusText` | text | The city's own status wording. |
| `severity` | text | NYC hazard class A, B or C, or Austin priority, where published. |
| `code` | text | Violation code, where published. |
| `category` | text | Category or type of the record. |
| `description` | text | Violation text (for Seattle, free text from complainants). |
| `address` | text | Property address. |
| `city` | text | City or borough. |
| `zip` | text | ZIP code (not published by Chicago, Cincinnati, Reading, New Orleans, Orlando and Norfolk). |
| `neighborhood` | text | Neighborhood, where published. |
| `latitude` | number | Latitude, when published. |
| `longitude` | number | Longitude, when published. |
| `caseNumber` | text | Case or notice number, where published. |
| `url` | text | Link to the city's lookup site or dataset. |
| `source` | text | The open-data dataset the record came from. |
| `scrapedAt` | datetime | When the Actor collected the record (UTC). |
| `inspectionStatus` | text | Chicago only: inspection status (for example FAILED). |
| `division` | text | San Francisco only: assigned DBI division. |
| `closedDate` | text | Austin only: date the case was closed, when it has been. |
| `lastUpdate` | text | Austin and Seattle: last update status or date from the city. |
| `repeatOffenderRelated` | boolean | Austin only: whether the case is flagged as related to a repeat offender. |
| `ownerName` | text | Philadelphia: owner of record from the city's property file, as published by Philadelphia L\&I. Chicago hearings: the respondent(s) named in the city's case (usually the owner, LLC or manager). |
| `hearingDate` | date | Chicago hearings and NYC OATH tickets only: hearing date (can be in the future). |
| `fineAmount` | number | Chicago hearings and NYC OATH tickets only: fine or penalty imposed (Chicago shows 0 while pending). |
| `balanceDue` | number | NYC OATH tickets only: penalty still unpaid, in dollars. |
| `noticeNumber` | text | Chicago hearings only: notice of violation number. |
| `parcelId` | text | Parcel or tax account number, where published (Philadelphia, Los Angeles, Orlando, Norfolk). |
| `noticeUrl` | text | Philadelphia only: link to the public notice of violation document, when published. |
| `complianceDeadline` | date | Norfolk only: date the city set for the violation to be fixed. |
| `propertyType` | text | Orlando only: property use, for example Single Family. |

Fields a source does not publish are `null`. Fields marked with a city name appear only on records from that city. Complainant names are never included. Owner names appear only for Philadelphia (owner of record) and Chicago hearings (the respondent named in the public case).

### "New since yesterday" alerts

Turn on **Only new** and the Actor remembers what it has already returned, so each scheduled run delivers only records you have not seen before.

1. Open the Actor in Apify Console and set the input, with **Only new since last run** switched on and a fixed alert name (`stateKey`). Example input:

```json
{
  "jurisdictions": ["nyc", "chicago", "sf"],
  "keyword": "mold",
  "openOnly": true,
  "openedWithinDays": 7,
  "maxResultsPerJurisdiction": 500,
  "maxResults": 5000,
  "onlyNew": true,
  "stateKey": "daily-open-mold-violations"
}
```

2. Click **Save as task**, then open **Schedules**, create a schedule (for example the cron expression `0 7 * * *` for every day at 7:00 in the time zone you pick) and add the task to it.
3. Under the task's **Integrations**, send the results to Slack, email, Google Sheets, a webhook or your own system.

NYC issues thousands of violations a week, so combine the schedule with a keyword, ZIP or address filter and a result cap.

The first run returns everything that matches your window (all matching records opened in the last 7 days); later runs return only unseen records. Use a different alert name for each task so each keeps its own memory. A run with nothing new returns no results.

### Cost per run

This Actor uses **pay-per-result pricing: $3.00 per 1,000 results ($0.003 per result)**, with the Apify platform fee included. You are charged for the records a run returns and nothing is added on top for platform usage. A run that finds nothing new returns no results, so it has no per-result charge. The **Max results** input caps what a run can return (and so what it can cost).

**Worked example:** a daily alert returning 50 new violations costs 50 × $0.003 = $0.15 per run, about $4.50 for a 30-day month. Pulling 20,000 NYC violations costs 20 × $3.00 = $60.00, so use filters.

The pricing is configured in Apify Console; the Pricing tab on this page is the authoritative source if it ever differs from this text.

### Example input and output

The output below comes from real test runs of this Actor. Email addresses are masked and very long text is shortened here; the Actor returns the full values.

Input used for the example:

```json
{
  "jurisdictions": ["nyc", "chicago", "sf", "austin"],
  "openOnly": true,
  "openedWithinDays": 7,
  "maxResultsPerJurisdiction": 1,
  "onlyNew": false
}
```

Output (the first 2 records of a test run):

```json
[
  {
    "jurisdiction": "New York City (HPD housing)",
    "jurisdictionCode": "nyc",
    "recordId": "19313651",
    "recordType": "violation",
    "openedDate": "2026-10-21",
    "status": "open",
    "statusText": "VIOLATION OPEN",
    "severity": "Class C (immediately hazardous)",
    "code": "530",
    "category": "HPD housing maintenance violation",
    "description": "§ 27-2005, 27-2007, 27-2041.1 HMC, §238, § 309; § 107 (2) ( C) MDL AND 28 RCNY §25-171: REPLACE OR REPAIR THE SELF-CLOSING DOORS THAT IS MISSING OR DEFECTIVE HINGE AT BUILDING ENTRANCE DOIR AT PUBLIC HALL, 1st STORY",
    "address": "1176 WALTON AVENUE",
    "city": "Bronx",
    "zip": "10452",
    "neighborhood": "Concourse-Concourse Village",
    "latitude": 40.83417,
    "longitude": -73.919989,
    "caseNumber": null,
    "url": "https://hpdonline.nyc.gov/HPDonline/",
    "source": "data.cityofnewyork.us (wvxf-dwi5)",
    "scrapedAt": "2026-10-23T12:55:45.940Z"
  },
  {
    "jurisdiction": "Chicago (building violations)",
    "jurisdictionCode": "chicago",
    "recordId": "7532475",
    "recordType": "violation",
    "openedDate": "2026-10-22",
    "status": "open",
    "statusText": "OPEN",
    "severity": null,
    "code": "EV1111",
    "category": "PERMIT (Elevator)",
    "description": "MAINTAIN OR REPAIR HYDRO ELEVA — Failed to maintain hydraulic elevator equipment provided at premises in safe and sound working condition. (13-196-590, 13-196-630(b), 18-30-001) — Comments: CITY RECALL TEST",
    "address": "2825 W HOWARD ST",
    "city": "Chicago",
    "zip": null,
    "neighborhood": null,
    "latitude": 42.0191929059,
    "longitude": -87.7005801751,
    "caseNumber": "14934399",
    "inspectionStatus": "FAILED",
    "url": "https://data.cityofchicago.org/Buildings/Building-Violations/22u3-xenr",
    "source": "data.cityofchicago.org (22u3-xenr)",
    "scrapedAt": "2026-10-23T12:55:46.683Z"
  }
]
```

### Limits worth knowing

- **NYC publishes about 17,000 violations a week**, so filter by ZIP, address or keyword, use open-only, and set a result cap.
- NYC, Chicago, San Francisco, Austin and Cincinnati are usually updated within a day or two; Seattle is updated daily.
- **Chicago (both feeds), Cincinnati, Reading, New Orleans, Orlando and Norfolk publish no ZIP code.** They are skipped (with a warning) when you filter by ZIP; use the address filter for them.
- **Los Angeles** publishes only open LADBS code enforcement cases with a case type (for example GENERAL, NAR, PACE, VEIP), not the violation text. Use it to spot newly opened cases by address or ZIP, and check the LADBS record for details.
- **New Orleans** publishes the violation and code section but no open/closed status, so its records are marked `other` and left out when **Open only** is on.
- **Orlando** includes tickets and sign cases as well as housing and lot cases; filter by keyword or look at `category`. Complainant comments are left out on purpose.
- Severity is only filled where the city publishes it: NYC hazard class A (non-hazardous), B (hazardous) or C (immediately hazardous), and Austin priority.
- Kansas City's feed stopped in 2021 and is not included.
- With a small per-city cap and Only new on, each run returns the next unseen batch.

### FAQ

#### Which cities are covered?

New York City (HPD housing and DOB building violations, including unsafe facade, construction and elevator violations; the DOB building-violations feed has no ZIP column, so use the address filter there. The DOB safety feed adds elevator, Local Law 97 emissions-report and facade violations with ZIP and lat/lon; NYC posts it in batches about 1 to 2 weeks behind, so use 30 days there. The NYCHA feed covers housing-code violations in New York City Housing Authority developments, with hazard class, development name, apartment, ZIP and BBL; it has no open/closed column, so status is "other"), Los Angeles (LADBS), Chicago, Philadelphia (L\&I), San Francisco, New Orleans, Orlando FL, Norfolk VA, Seattle, Austin, Cincinnati and Montgomery County, Maryland (Bethesda, Silver Spring, Rockville and the rest of the county's housing code inspections; the county posts records after inspection, so the newest week can look thin) and Reading, Pennsylvania (rental, zoning and property-maintenance citations, with compliance deadlines; this feed has no ZIP column, so use the address filter there). We only add feeds that are public, current and keyless.

#### NYC returns thousands of rows. How do I narrow it?

Add a ZIP, an address, a keyword such as "mold" or "lead", turn on open-only and set a result cap.

#### Can I get Chicago properties headed to a building code hearing, with the owner's name?

Yes. Choose `chicago_hearings`. Each record is one cited violation in a City of Chicago Department of Administrative Hearings building case, with the address, ward, the respondent(s) named in the case (`ownerName`, often the owning LLC), the violation, the hearing date, the disposition (Pending, Continuance, Liable, Default, Non-Suit) and any fine. Pending and continued cases count as open. The date filter uses the hearing date, so set an end date in the future to see upcoming hearings, a common lead list for investors, wholesalers and property managers:

```json
{
  "jurisdictions": ["chicago_hearings"],
  "openOnly": true,
  "startDate": "2026-11-18",
  "endDate": "2027-01-31",
  "keyword": "porch"
}
```

#### Can I get NYC buildings with unpaid DOB / ECB penalties and the owner's name?

Yes. Choose `nyc_oath_dob`. Each record is one Department of Buildings (ECB) ticket heard at NYC OATH, with the property address, ZIP, borough-block-lot (`parcelId`), the respondent (`ownerName`, usually the owning LLC or the owner), the charge, the inspector's description, the penalty (`fineAmount`), the unpaid amount (`balanceDue`), the hearing date (`hearingDate`, often 2 to 3 months out) and the hearing status. A ticket counts as open while its hearing is pending or a balance is due. The date filter uses the date the ticket was written. Investors, wholesalers, expediters and property managers use it as a list of owners facing city penalties:

```json
{
  "jurisdictions": ["nyc_oath_dob"],
  "openOnly": true,
  "openedWithinDays": 30,
  "zipCodes": ["11233", "10467"]
}
```

#### Can I get NYC Local Law 97 (LL97) or elevator violation lists?

Yes. Pick the `nyc_dob_safety` jurisdiction and add a keyword: "LL97" returns buildings cited for failing to file their Local Law 97 greenhouse-gas emissions report (address, ZIP, borough, BIN and BBL), and "elevator" returns elevator device violations. Energy and compliance consultants, elevator contractors and property managers use these as lead and to-do lists. Example input: `{"jurisdictions": ["nyc_dob_safety"], "keyword": "LL97", "openOnly": true, "openedWithinDays": 365, "maxResults": 500}`. LL97 citations are issued in yearly batches, so use a long date window for them.

#### Is this the same as building permits?

No. Permits show planned work; violations show enforcement problems. See the building permits Actor below.

#### Does it include owner names?

For Philadelphia, where the city publishes the owner of record, and for Chicago building code hearings, where the city publishes the named respondent (`ownerName`). Elsewhere you get the property address, parcel number where published, and the violation, which you can match to county assessor records.

#### Why do some fields say null?

Cities publish different columns, so a field is null when the city does not publish it.

### Related Actors

More Actors from GovData Feeds, all on Apify:

- [sam-gov-opportunities-alerts](https://apify.com/radiant_opuntia/sam-gov-opportunities-alerts): New SAM.gov federal contract opportunities and bid alerts
- [grants-gov-alerts](https://apify.com/radiant_opuntia/grants-gov-alerts): US federal grant opportunities (Grants.gov): ceilings, deadlines, eligibility
- [sec-form-d-alerts](https://apify.com/radiant_opuntia/sec-form-d-alerts): SEC Form D filings: companies that just raised money
- [usaspending-awards-alerts](https://apify.com/radiant_opuntia/usaspending-awards-alerts): New federal contract, grant and loan awards (USAspending)
- [sec-form4-insider-alerts](https://apify.com/radiant_opuntia/sec-form4-insider-alerts): SEC Form 4 insider buys and sells, one row per transaction
- [fda-recall-alerts](https://apify.com/radiant_opuntia/fda-recall-alerts): FDA food, drug and medical device recalls
- [fda-compliance-alerts](https://apify.com/radiant_opuntia/fda-compliance-alerts): FDA 510(k) clearances, MAUDE adverse events and warning letters
- [cpsc-recall-alerts](https://apify.com/radiant_opuntia/cpsc-recall-alerts): CPSC consumer product safety recalls
- [us-building-permits-alerts](https://apify.com/radiant_opuntia/us-building-permits-alerts): New building permits from nine city open-data portals
- [clinical-trials-alerts](https://apify.com/radiant_opuntia/clinical-trials-alerts): New ClinicalTrials.gov studies by condition, sponsor and phase
- [federal-register-alerts](https://apify.com/radiant_opuntia/federal-register-alerts): Federal Register rules, proposed rules and notices
- [contractor-license-alerts](https://apify.com/radiant_opuntia/contractor-license-alerts): New contractor licenses in WA, OR and NY with bond and insurance
- [ofac-sanctions-alerts](https://apify.com/radiant_opuntia/ofac-sanctions-alerts): OFAC sanctions screening and change alerts
- [new-business-registrations-alerts](https://apify.com/radiant_opuntia/new-business-registrations-alerts): New LLC and corporation registrations (NY, CO, OR, CT)
- [epa-echo-enforcement-alerts](https://apify.com/radiant_opuntia/epa-echo-enforcement-alerts): EPA ECHO facilities with new environmental penalties
- [restaurant-inspections-alerts](https://apify.com/radiant_opuntia/restaurant-inspections-alerts): Restaurant health inspections from seven US jurisdictions

*Data comes from city open-data portals and is public record. This Actor is not affiliated with any city. Violation data can be delayed, incomplete or corrected later; check the official city record before taking action against an owner or business.*

# Actor input Schema

## `jurisdictions` (type: `array`):

Which city feeds to search. Leave empty for all.

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

Words in the violation text, e.g. "mold", "rodent", "elevator", "fire", "unsafe". Leave empty for all.

## `address` (type: `string`):

Part of the street or address, e.g. "broadway", "123 main". Leave empty for all.

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

Only these 5-digit ZIP codes. Chicago (both feeds), Cincinnati, Reading PA, New Orleans, Orlando and Norfolk publish no ZIP in their data and are skipped when this is set (use the address filter for them).

## `recordTypes` (type: `array`):

violation = a cited violation / notice of violation. complaint = a complaint or service request that may lead to one. Leave empty for both.

## `openOnly` (type: `boolean`):

Only violations that are still open (not complied, closed or resolved). New Orleans publishes no status, so its records are left out when this is on.

## `openedWithinDays` (type: `integer`):

Look back window by violation / complaint date. Ignored if a start date is set. NYC alone has thousands of new violations per day, so combine with a ZIP, address or keyword filter.

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

YYYY-MM-DD. Overrides the look back.

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

YYYY-MM-DD. Defaults to today.

## `onlyNew` (type: `boolean`):

Skip records already returned by an earlier run with the same alert name. Use with a schedule for alerts.

## `stateKey` (type: `string`):

Name for this alert so several schedules do not share memory, e.g. "bronx-mold". Leave empty to derive it from the filters.

## `socrataAppToken` (type: `string`):

Optional free token from the city data portal for higher rate limits. Not needed for normal use.

## `maxResultsPerJurisdiction` (type: `integer`):

Cap per city. With only new on, the next run returns the next batch.

## `maxResults` (type: `integer`):

Overall cap across cities.

## Actor input object example

```json
{
  "jurisdictions": [],
  "keyword": "",
  "address": "",
  "zipCodes": [],
  "recordTypes": [],
  "openOnly": false,
  "openedWithinDays": 7,
  "startDate": "",
  "endDate": "",
  "onlyNew": false,
  "stateKey": "",
  "maxResultsPerJurisdiction": 25,
  "maxResults": 50
}
```

# Actor output Schema

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

All violation records returned by this run (flat JSON items in the default dataset).

## `runSummary` (type: `string`):

Counts of items pushed and items skipped as already seen (only-new mode).

# 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 = {
    "keyword": "",
    "address": "",
    "openOnly": false,
    "openedWithinDays": 7,
    "startDate": "",
    "endDate": "",
    "onlyNew": false,
    "stateKey": "",
    "maxResultsPerJurisdiction": 25,
    "maxResults": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("radiant_opuntia/code-violations-alerts").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 = {
    "keyword": "",
    "address": "",
    "openOnly": False,
    "openedWithinDays": 7,
    "startDate": "",
    "endDate": "",
    "onlyNew": False,
    "stateKey": "",
    "maxResultsPerJurisdiction": 25,
    "maxResults": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("radiant_opuntia/code-violations-alerts").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 '{
  "keyword": "",
  "address": "",
  "openOnly": false,
  "openedWithinDays": 7,
  "startDate": "",
  "endDate": "",
  "onlyNew": false,
  "stateKey": "",
  "maxResultsPerJurisdiction": 25,
  "maxResults": 50
}' |
apify call radiant_opuntia/code-violations-alerts --silent --output-dataset

```

## MCP server setup

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

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/X2ds1M70R87XkZfze/builds/1GdY4aYgOUByddIa0/openapi.json
