# Restaurant Health Inspections Scraper: Violations & Alerts (`radiant_opuntia/restaurant-inspections-alerts`) Actor

Get alerts for new restaurant health inspections, fails, closures and critical violations across NYC, Chicago, Austin, King County/Seattle, New York State, Delaware and Marin County. One normalized format. Filter by name, city, ZIP, outcome. 'Only new' mode. No API key.

- **URL**: https://apify.com/radiant_opuntia/restaurant-inspections-alerts.md
- **Developed by:** [GovData Feeds](https://apify.com/radiant_opuntia) (community)
- **Categories:** Lead generation
- **Features:** Limited permissions
- **Stats:** 2 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 restaurant health inspections from seven US jurisdictions in one format, with a normalized outcome (pass, conditional, fail, closed), score, violations and location.**

**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/restaurant-inspections-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, Chicago, Austin, King County (Seattle), New York State (outside NYC), Delaware and Marin County (CA)** and returns one flat record per inspection: **business name, address, ZIP, inspection date and type, a normalized outcome (pass, conditional, fail, closed, violations, reopened, other), the original outcome text, score and grade where published, violation count and critical violation count, the violation text, latitude and longitude, and NYC phone numbers**.

Filter by jurisdiction, business name keyword, city or borough, ZIP, outcome, a **problems only** switch (fails, closures, red placards and critical violations) and inspection date window. Turn on **Only new** for a daily or weekly alert.

#### Use cases

- **Restaurant groups and franchisors:** watch your own locations and competitors for fails and closures.
- **Pest-control, cleaning, hood-cleaning and food-safety consultants:** find businesses that just failed an inspection.
- **Food-delivery and review platforms:** add inspection flags to listings.
- **Insurers, lenders and commercial brokers:** monitor food-service tenants and borrowers.
- **Journalists and local-news teams:** automate a weekly "restaurants that failed" story.
- **AI agents:** answer "which restaurants in 10011 failed an inspection 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: seven different health-department feeds become one format.

| What you need | Official site / API | This Actor |
|---|---|---|
| Covering several jurisdictions | Each department has its own portal, columns and rating system | One input and one record format |
| Comparing outcomes | Different wording everywhere (scores, grades, placards, pass/fail) | A normalized `outcome` plus the original `outcomeText` |
| One row per inspection | NYC, King County, New York State and Delaware publish one row per violation | Violations are grouped into one record per inspection, with counts and text |
| Finding only the bad ones | Filter each feed differently | A single **problems only** switch |
| Only new inspections | 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 jurisdiction. |
| `jurisdictionCode` | text | nyc, chicago, austin, king, ny_state, delaware or marin. |
| `inspectionId` | text | Inspection identifier (built from the source fields where the source has none). |
| `inspectionDate` | date | Inspection date. |
| `businessId` | text | Business identifier from the source. |
| `businessName` | text | Business name. |
| `address` | text | Address. |
| `city` | text | City or borough, when reliable. |
| `zip` | text | ZIP code. |
| `businessType` | text | Cuisine or facility type, when published. |
| `inspectionType` | text | Inspection type as published. |
| `outcome` | text | Normalized outcome: pass, conditional, fail, closed, violations, reopened or other. |
| `outcomeText` | text | The jurisdiction's own outcome wording. |
| `score` | integer | Numeric score, only where published (NYC, Austin, King County). |
| `grade` | text | Grade, where published. |
| `violationCount` | integer | Number of violations cited. |
| `criticalViolationCount` | integer | Number of critical violations (Chicago: priority violations, items 1 to 14). |
| `violations` | text | Violation text, shortened to about 1,500 characters. |
| `latitude` | number | Latitude, when published. |
| `longitude` | number | Longitude, when published. |
| `phone` | text | Phone number, where published (NYC). |
| `url` | text | Link to the official inspection search or record. |
| `source` | text | The open-data dataset the record came from. |
| `scrapedAt` | datetime | When the Actor collected the record (UTC). |
| `riskCategory` | text | Chicago and King County only: risk category as published. |
| `violationPoints` | integer | King County only: total violation points for the inspection. |

Fields a source does not publish are `null`. In NYC and King County a lower score is better; in Austin a higher score is better (below 70 is a fail). Chicago, Marin and the state feeds publish a result but no numeric score.

### "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", "king"],
  "problemsOnly": true,
  "inspectedWithinDays": 14,
  "maxResultsPerJurisdiction": 500,
  "maxResults": 5000,
  "onlyNew": true,
  "stateKey": "weekly-restaurant-fails"
}
```

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.

Some feeds lag (Austin about a month, New York State about a week), so use a window of 14 days or more for a weekly alert.

The first run returns everything that matches your window (all matching inspections in the window); 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 weekly alert returning 80 failed or closed inspections costs 80 × $0.003 = $0.24 per run. Pulling 10,000 inspections costs $30.00.

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", "king"],
  "problemsOnly": true,
  "inspectedWithinDays": 7,
  "maxResultsPerJurisdiction": 1,
  "onlyNew": false
}
```

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

```json
[
  {
    "jurisdiction": "New York City",
    "jurisdictionCode": "nyc",
    "inspectionId": "40386619-2026-10-20-cycle-inspection-initial",
    "inspectionDate": "2026-10-20",
    "businessId": "40386619",
    "businessName": "OPTO",
    "address": "35 WEST 20 STREET",
    "city": "Manhattan",
    "zip": "10011",
    "businessType": "Mediterranean",
    "inspectionType": "Cycle Inspection / Initial Inspection",
    "outcome": "violations",
    "outcomeText": "Violations were cited in the following area(s).",
    "score": 13,
    "grade": "A",
    "violationCount": 2,
    "criticalViolationCount": 2,
    "violations": "06C (critical): Food, supplies, or equipment not protected from potential source of contamination during storage, preparation, transportation, display, service or from customer’s refillable, reusable container. Condiment…",
    "latitude": 40.740205545887,
    "longitude": -73.992205329697,
    "phone": "2124637890",
    "url": "https://a816-health.nyc.gov/ABCEatsRestaurants/#!/Search",
    "source": "data.cityofnewyork.us (43nn-pn8j)",
    "scrapedAt": "2026-10-23T12:51:25.570Z"
  },
  {
    "jurisdiction": "Chicago",
    "jurisdictionCode": "chicago",
    "inspectionId": "2645649",
    "inspectionDate": "2026-10-22",
    "businessId": "34220",
    "businessName": "MACARONI GRILL",
    "address": "11601 W TOUHY AVE",
    "city": "CHICAGO",
    "zip": "60666",
    "businessType": "Restaurant",
    "inspectionType": "Canvass Re-Inspection",
    "outcome": "fail",
    "outcomeText": "Fail",
    "score": null,
    "grade": null,
    "riskCategory": "Risk 1 (High)",
    "violationCount": 5,
    "criticalViolationCount": 0,
    "violations": "49. NON-FOOD/FOOD CONTACT SURFACES CLEAN - Comments: OBSERVED PIPES AND EQUIPMENT THROUGHOUT FACILITY WITH GREASE AND SOIL BUILD UP. INSTRUCTED MANAGER TO CLEAN AND MAINTAIN EQUIPMENT THROUGHOUT KITCHEN AND BAR AREAS. IN…",
    "latitude": 42.00875076599798,
    "longitude": -87.90687413400109,
    "url": "https://www.chicago.gov/city/en/depts/cdph/provdrs/healthy_restaurants/svcs/food-protection-inspection-search.html",
    "source": "data.cityofchicago.org (4ijn-s7e5)",
    "scrapedAt": "2026-10-23T12:51:26.452Z"
  }
]
```

### Limits worth knowing

- **Feed lag differs:** NYC, Chicago, King County, Delaware and Marin are usually updated daily or within a few days; New York State lags about a week and Austin about a month.
- Score and grade are only filled where the jurisdiction publishes them, and they mean different things in different places.
- `outcome` is normalized by the Actor; New York State and Delaware publish violations without a pass or fail, so they show as `violations`.
- Austin's city field is not reliable, so it is left empty; its ZIP and address are kept.
- Only feeds that are public, current and keyless are included. Several cities were left out because their data is stale or requires a login.
- Inspector names are deliberately not included.
- With a small per-jurisdiction cap and Only new on, each run returns the next unseen batch.

### FAQ

#### Which places are covered?

New York City, Chicago, Austin (TX), King County / Seattle (WA), New York State outside NYC, Delaware and Marin County (CA).

#### Can you add my city?

We only add feeds that are public, current and keyless. Tell us which city you need.

#### Why is the score empty for some places?

Some places publish a result (pass/fail or a color placard) but no number.

#### Do I get the violation text?

Yes, in `violations` (shortened to about 1,500 characters).

#### Is business contact data included?

Only what the jurisdiction publishes: name, address and, in NYC, the restaurant phone number.

### 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
- [code-violations-alerts](https://apify.com/radiant_opuntia/code-violations-alerts): Building, housing and property code violations from six cities

*Data comes from city, county and state open-data portals and is public record. This Actor is not affiliated with any health department. Inspection data can be delayed, incomplete or corrected later; check the official source before taking action against a business.*

# Actor input Schema

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

Which city / county / state health department feeds to search. Leave empty for all.

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

Part of the restaurant / business name, e.g. "pizza", "mcdonald". Leave empty for all.

## `cities` (type: `array`):

Only these cities / boroughs (NYC: Manhattan, Brooklyn, Queens, Bronx, Staten Island). Leave empty for all.

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

Only these 5-digit ZIP codes. Leave empty for all.

## `outcomes` (type: `array`):

Only these normalized outcomes. Leave empty for all.

## `problemsOnly` (type: `boolean`):

Only failed or closed inspections, red placards, or inspections with critical violations.

## `inspectedWithinDays` (type: `integer`):

Look back window. Some feeds lag by days or weeks (Austin about a month, New York State about a week), so use 14 or more for a weekly alert. Ignored if a start date is set.

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

YYYY-MM-DD. Overrides the look back.

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

YYYY-MM-DD. Defaults to today.

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

Skip inspections 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. "nyc-pizza-fails". Leave empty to derive it from the filters.

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

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

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

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

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

Overall cap across feeds.

## Actor input object example

```json
{
  "jurisdictions": [],
  "keyword": "",
  "cities": [],
  "zipCodes": [],
  "outcomes": [],
  "problemsOnly": false,
  "inspectedWithinDays": 7,
  "startDate": "",
  "endDate": "",
  "onlyNew": false,
  "stateKey": "",
  "maxResultsPerJurisdiction": 25,
  "maxResults": 50
}
```

# Actor output Schema

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

All inspection 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": "",
    "problemsOnly": false,
    "inspectedWithinDays": 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/restaurant-inspections-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": "",
    "problemsOnly": False,
    "inspectedWithinDays": 7,
    "startDate": "",
    "endDate": "",
    "onlyNew": False,
    "stateKey": "",
    "maxResultsPerJurisdiction": 25,
    "maxResults": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("radiant_opuntia/restaurant-inspections-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": "",
  "problemsOnly": false,
  "inspectedWithinDays": 7,
  "startDate": "",
  "endDate": "",
  "onlyNew": false,
  "stateKey": "",
  "maxResultsPerJurisdiction": 25,
  "maxResults": 50
}' |
apify call radiant_opuntia/restaurant-inspections-alerts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,radiant_opuntia/restaurant-inspections-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/Z0OI31yvIkJV85tsV/builds/w91RmIdZCKS97mec3/openapi.json
